-
-
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
0.38.0 still throwing errors #2944
Comments
Additional Information 2I've reverted the changes to my snippet:
This is the file in question:
There's no way this should be reported as string literal offense. |
I think the problem is this one: #2802
|
that would explain the frozen string literal at least. |
The only error I can repro is caused by:
...in |
that's just a copy paste error, didn't want our file structure in there. |
In that case I can't reproduce your problem at all. |
I'll run a -d tommorow on the files throwing it on my side |
going to close this. Reinstalled Rubocop again and now it wll worked fine. |
sigh, Sorry reopening this.
The file in question is a standard spec file, but contains again a multiline string with a mix of single and double quotes. |
Here's a slightly modified file that is throwing the errors:
|
and writing it like this fixes it:
|
I've rewritten all our offensive files using this structure:
and all the Rubocop errors dissapeared.
Rubocop throws out the above mentioned errors. |
Thanks for the update. I will probably be able to find it with this extra On Mon, Mar 14, 2016 at 2:44 PM, Arne De Herdt [email protected]
|
If you need more input from my side, just let me know and I'll be happy to help out. Also, writing the code in heredoc style seems to work as well:
|
Okay,
I reported before that the
Style/StringLiterals
cop was generating errors in the0.37.2
error.Today I upgraded Rubocop to version
0.38.0
on a separate branch and tried to run it again to see what has changed.Expected behavior
No new errors should be generated
Existing code should not marked as violations
Actual behavior
The current code base suddenly get's marked as violations for specific cops
Steps to reproduce the problem
0.38.0
from0.37.2
.rubocop.yml
.rubocop_todo.yml
RuboCop version
Include the output of
rubocop -V
:Additional information
But when I try this:
So something is off when running RUbocop over all files.
The text was updated successfully, but these errors were encountered: