-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Problem with Naming/MethodName: EnforcedStyle: camelCase and '_' or 'i' variables #8132
Comments
Good catch. A pull request would be great. Best use a no-capture |
/^@{0,2}_?(?:[a-z]|[a-z][\da-zA-Z]+)?[!?=]?$/ - OK? |
|
Yes. |
avrusanov
pushed a commit
to avrusanov/rubocop
that referenced
this issue
Jun 11, 2020
…yle: camelCase and _ or i variables.
avrusanov
pushed a commit
to avrusanov/rubocop
that referenced
this issue
Jun 12, 2020
avrusanov
pushed a commit
to avrusanov/rubocop
that referenced
this issue
Jun 12, 2020
…yle: camelCase and _ or i variables.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
We use:
rubocop -V
0.85.0 (using Parser 2.7.1.3, rubocop-ast 0.0.3, running on ruby 2.4.5 x86_64-darwin18)
We have problem with cop
Naming/MethodName:
EnforcedStyle: camelCase
and '_' or 'i' variables.
We have offences like that:
For fixing that line needs to be changed:
https://github.com/rubocop-hq/rubocop/blob/971769a0a01c55d9b23a29ae8d5b3ab45f637152/lib/rubocop/cop/mixin/configurable_naming.rb#L12
From
To:
I can create pull request if acceptable
The text was updated successfully, but these errors were encountered: