-
-
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
Style/SpecialGlobalVars auto-gen-config behaviour change #2556
Comments
Does it make a difference if you delete the |
no, deleting Now that I test it a bit more I realise that I'm having this issue with several cops so maybe there's something else going on (my expected workflow is to run
|
Style/WordArray may have changed its configuration in a similar way to Style/SpecialGlobalVars by adding |
All those cops have changed recently. |
Can you give a standalone file which I can run |
ok, for Style/SpecialGlobalVars create this simple file:
|
Awesome, with repro this should be easy to debug. |
I have a fix for this. Do you have a sample showing the same problem with WordArray, etc.? |
Just been trying to get a good sample for GuardClause but put in its own thread, maybe it should be here? #2557 |
No, it's better to keep it in a separate issue. I've answered there and I think it's not the same problem. |
Fixed for the test case, but still broken for a different test case (sorry!): test_varnames1.rb:
tested with bc3e40a |
I caused that bug in 5673c6f. Looking for the best way to fix it. |
My open PR has a fix. |
In the process of tidying up an old codebase, have fixed some instances of Style/SpecialGlobalVars offenses but have more that I want to ignore with
--auto-gen-config
. v0.35.1 put this in~/.rubocop_todo.yml
:as of git version 1716abb rubocop creates this instead:
which means that when I run rubocop I get alerted to the files that I've already fixed the offense in & breaks my incremental improvement workflow.
The text was updated successfully, but these errors were encountered: