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
RuboCop exception handling of autocorrecting cop has multiple issues #8016
Comments
marcandre
added a commit
to marcandre/rubocop
that referenced
this issue
May 23, 2020
It tests the same thing as the previous spec; their success is not independent. See [rubocop#8016]
marcandre
added a commit
to marcandre/rubocop
that referenced
this issue
May 23, 2020
marcandre
added a commit
to marcandre/rubocop
that referenced
this issue
May 30, 2020
It tests the same thing as the previous spec; their success is not independent. See [rubocop#8016]
marcandre
added a commit
to marcandre/rubocop
that referenced
this issue
May 30, 2020
marcandre
added a commit
to marcandre/rubocop
that referenced
this issue
May 31, 2020
It tests the same thing as the previous spec; their success is not independent. See [rubocop#8016]
marcandre
added a commit
that referenced
this issue
May 31, 2020
It tests the same thing as the previous spec; their success is not independent. See [#8016]
I believe this to be fixed in #7868 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While working on #7868, I realized that RuboCop's exception handling of autocorrecting cop has issues:
rubocop
(move theraise
inside the->
in the example above)There are 3 specs for this handling in
team_spec
, but 1 is redundant with the previous spec, and there are quite a few cases missing and don't test the interaction withRunner
. For example this spec fails if we addlet(:options) { { auto_correct: true } }
.I don't intend on cleaning this up before #7868 is completed. It should be easier to deal with too as the current autocorrection timing is quite intricate.
The text was updated successfully, but these errors were encountered: