-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of form-2 subs in defview #11148
Conversation
Jenkins Builds
|
i still think form-2 should be used, if you need to pass a parameter from another subscription, that means subscriptions was incorrectly designed |
@flexsurfer please elaborate why form-2 should be used (just reminder) |
We have a safe way to not care about "incorrect design" (that's kind of arguable) and bugs caused by it, so what's the reason to not use it? |
yeah i know it will work, and its not critical, it's just my personal preference, however, i don't mind to follow any team's decision, and i know most devs for removing defview, so i'll approve this PR, but suggest to replace |
that's fine, but this PR is not about removing
I would also consider some punishment for the retard who introduced |
100% of end-end tests have passed
Passed tests (99)Click to expand
|
e3126e2
to
f9df0f3
Compare
We don't need form-2 subs and those subs cause bugs in
defview
when they have parameters. This PR solves it. Next step would be removingdefview
from code.status: ready