add suppress warning option to allow rubocop to continue #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
My project uses Rubocop 67.0 and without this PR, I am unable to use rubocop with VScode. |
|
Thanks for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We often use a shared rubocop.yml file across multiple projects. When then parent config files is updated to include new cops but one of the consuming projects is using an older version of rubocop, rubocop will report that there are unrecognized cops. These are just warnings and shouldn't cause rubocop to fail entirely.
This PR just adds a suppress warning option to the configuration to ignore errors and run regardless. I figured anyone with a similar project configuration that often runs into issues like this might benefit from being able to toggle it on and off as they see fit.