-
Notifications
You must be signed in to change notification settings - Fork 160
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
allow immutable state variables to be named in CAPS_SNAKE_CASE #243
Comments
I think we need to rethink the whole approach to naming, since it's hard to make some calls. For example, the linked docs use mixedCase for immutable variables, but I agree that it makes sense to use SNAKE_CASE. The quick and backward compatible fix here is to add an option to the |
It's hard to think of a good single setting here, since it really concerns two rules. The simplest way would be to have some "general config" option |
Yeah, I'd be fine with that. Especially because having such a long and ugly option would motivate me to totally redo the naming rules in the next major 😄 |
I don't know what is the state of this issue now but having support for this would be great 👍 |
Plus one, would love to see this! |
+1 on this, would be great, Optimism prefers |
+1 here too guys |
agree, let's add the snake case |
Are any updates? |
yes,please ! |
see this PR |
This is more of a question than a bug report -- IMO immutable variables should be allowed to be treated as constants, since they in fact cannot be changed.
Currently the code below returns a
warning Variable name must be in mixedCase
when linted with the recommended ruleset.The text was updated successfully, but these errors were encountered: