-
Notifications
You must be signed in to change notification settings - Fork 208
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
lint against throw Fail
#10118
Comments
The reasons to use
If you really want to weed out the redundancy of |
Issues for 1-2,
The latter might get done, since the PR had some positive feedback, |
Closing this for now with the expectation that 51426 will be fixed eventually. Then we can ban |
What is the Problem Being Solved?
It's redundant and seeing it trains people to be lax in when errors are created vs thrown.
Description of the Design
Fail
is only for thecondition || Fail
pattern.throw Fail
is not allowed.Bonus points for auto-fixing to
throw makeError
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: