We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a warning Warning: unrecognized cop is raised we expect to exit with status code 1.
Warning: unrecognized cop
rubocop exits with code 0.
rubocop
Using rubocop --fail-level=warning or Lint: Severity: warning option has no effect.
rubocop --fail-level=warning
Lint: Severity: warning
mkdir test-rubocop cd test-rubocop echo "Syntax/Whatever:\n Enabled: true" > .rubocop.yml rubocop echo $?
0 is printed, 1 should be printed because a warning is raised.
0.73.0
The text was updated successfully, but these errors were encountered:
It makes sense that rubocop --fail-level=warning should include this.
Sorry, something went wrong.
ff811f0
Merge pull request #7526 from jethroo/fix/Issue_7231_unrecognized_cop…
3c5881e
…_warning_does_not_exit_with_1 Fix #7231 unknown cop in config file will exit with code 2
No branches or pull requests
Expected behavior
When a warning
Warning: unrecognized cop
is raised we expect to exit with status code 1.Actual behavior
rubocop
exits with code 0.Using
rubocop --fail-level=warning
orLint: Severity: warning
option has no effect.Steps to reproduce the problem
0 is printed, 1 should be printed because a warning is raised.
RuboCop version
0.73.0
The text was updated successfully, but these errors were encountered: