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 think setter methods should never be reported by this cop. The user shouldn't have to add them to the IgnoredMethods configuration option.
IgnoredMethods
$ echo 'x.y = 1' | rubocop --only Style/MethodCallWithArgsParentheses --stdin stdin.rb Inspecting 1 file . 1 file inspected, no offenses detected
$ echo 'x.y = 1' | rubocop --only Style/MethodCallWithArgsParentheses --stdin stdin.rb Inspecting 1 file C Offenses: stdin.rb:1:3: C: Use parentheses for method calls with arguments. x.y = 1 ^ 1 file inspected, 1 offense detected
Run the above command.
Current master. The problem does not occur on 0.47.1.
master
0.47.1
The text was updated successfully, but these errors were encountered:
Agree with you @jonas054. Looks like a very meaningful adjustment.
Sorry, something went wrong.
Agreed.
[Fix rubocop#4152] Make Style/MethodCallWithArgsParentheses not req…
Style/MethodCallWithArgsParentheses
659cc08
…uire parens on setters This cop would register an offense for setter methods without parens, e.g.: ``` foo.bar = baz ``` This change fixes that.
7f801a6
No branches or pull requests
I think setter methods should never be reported by this cop. The user shouldn't have to add them to the
IgnoredMethods
configuration option.Expected behavior
Actual behavior
Steps to reproduce the problem
Run the above command.
RuboCop version
Current
master
. The problem does not occur on0.47.1
.The text was updated successfully, but these errors were encountered: