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
I ran into this error that I think is caused by the safe navigation operator.
No error when running Lint/AmbiguousOperator on a file containing something like foo&.* -1
Lint/AmbiguousOperator
foo&.* -1
undefined method `arguments' for nil:NilClass gems/rubocop-0.90.0/lib/rubocop/cop/util.rb:37:in `add_parentheses' gems/rubocop-0.90.0/lib/rubocop/cop/lint/ambiguous_operator.rb:51:in `block (2 levels) in on_new_investigation' ...
Run rubocop --only Lint/AmbiguousOperator -d --force-default-config on a file containing foo&.* -1
rubocop --only Lint/AmbiguousOperator -d --force-default-config
$ [bundle exec] rubocop -V 0.90.0 (using Parser 2.7.1.4, rubocop-ast 0.4.0, running on ruby 2.5.7 x86_64-darwin18)
The text was updated successfully, but these errors were encountered:
[Fix rubocop#8704] Fix an error for Lint/AmbiguousOperator
099af2d
Fixes rubocop#8704. This PR fixes an error for `Lint/AmbiguousOperator` when using safe navigation operator with a unary operator.
[Fix #8704] Fix an error for Lint/AmbiguousOperator
134068f
Fixes #8704. This PR fixes an error for `Lint/AmbiguousOperator` when using safe navigation operator with a unary operator.
Successfully merging a pull request may close this issue.
I ran into this error that I think is caused by the safe navigation operator.
Expected behavior
No error when running
Lint/AmbiguousOperator
on a file containing something likefoo&.* -1
Actual behavior
Steps to reproduce the problem
Run
rubocop --only Lint/AmbiguousOperator -d --force-default-config
on a file containingfoo&.* -1
RuboCop version
The text was updated successfully, but these errors were encountered: