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
Per the documentation, it appears you can't use AllowComments unless the documentation has a typo?
AllowComments
When running Rubocop, I see the following output:
Use the following Rubocop configuration:
Lint/EmptyInPattern: Enabled: true AllowComments: false
Then run Rubocop on any Ruby file with the above configuration to see the behavior shown above.
1.16.0 (using Parser 3.0.1.1, rubocop-ast 1.7.0, running on ruby 3.0.1 arm64-darwin20) - rubocop-performance 1.11.3 - rubocop-rake 0.5.1 - rubocop-rspec 2.3.0
The text was updated successfully, but these errors were encountered:
[Fix rubocop#9850] Fix missing option for Lint/EmptyInPattern
Lint/EmptyInPattern
ba141f5
Fixes rubocop#9850. This PR fixes missing `AllowComments` option for `Lint/EmptyInPattern`.
Merge pull request #9851 from koic/fix_missing_option_for_lint_empty_…
632e2f1
…in_pattern [Fix #9850] Fix missing option for `Lint/EmptyInPattern`
Successfully merging a pull request may close this issue.
Expected behavior
Per the documentation, it appears you can't use
AllowComments
unless the documentation has a typo?Actual behavior
When running Rubocop, I see the following output:
Steps to reproduce the problem
Use the following Rubocop configuration:
Then run Rubocop on any Ruby file with the above configuration to see the behavior shown above.
RuboCop version
The text was updated successfully, but these errors were encountered: