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.
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.