-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Is there a way to ignore rubocop warnings? #1418
Comments
In fact
|
Write a wrapper around rubocop and point
And thus I'm supposed to fix it. How nice.
Nope, we're arseholes all the way down.
Write another wrapper? |
Sorry, not sure what ticked you off, I simply removed the warning from parser itself. Thank you for pointing me to the wrapper thing, couldn't find a way how to do it. |
Not ticked off at all, that was supposed to self irony. Syntastic maintainer blames rubocop. Rubocop maintainer blames parser. Parser maintainer blames ruby. And the funny thing is, each of us have reasons for doing it (aside from being arseholes, that is). :) |
For what it's worth: I added a note to the wiki with the current workarounds. |
Thank you, this definitely helps. |
Another way around this is to uninstall the current version of parser and install an older version that supports the syntax for your version of ruby? Look in https://github.com/whitequark/parser/blob/v2.2.3.0/lib/parser/current.rb, find your ruby version, then go back through the tags until you find the tag that supports your version of ruby? For example for ruby version 2.1.6, I had to install parser 2.2.2.6. update: just noticed you said you are working with other developers, with a number of dependencies, so maybe this isn't an option? |
I have just edited the local gem and commented the warnings out. |
Depending on some factors rubocop is showing this line sometimes:
Since I am in a project with other developers and dependencies I can't do shit about it and it blows up Syntastic.
I was told to run it with
ruby -W0 -S
, okay, fair enough. How can I do that?Or is there a better way?
The text was updated successfully, but these errors were encountered: