We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Had a couple of these in our codebase that we didn't like. fatalErrors should always include an informative message.
The text was updated successfully, but these errors were encountered:
This is a great first rule to write, if anyone's interested.
Sorry, something went wrong.
It sounds like a great rule!
Implemented on #1365 ✅
No branches or pull requests
Had a couple of these in our codebase that we didn't like. fatalErrors should always include an informative message.
The text was updated successfully, but these errors were encountered: