We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
bbatsov
koic
Learn more about funding links in repositories.
Report abuse
There was an error while loading. Please reload this page.
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
Expected cops to run without errors being raised
The following errors occured: An error occurred while Layout/EmptyLinesAroundArguments cop was inspecting .....
An error occurred while Layout/EmptyLinesAroundArguments cop was inspecting .....
Anywhere I use the call syntax, with the arguments on the next line, I get a hard error for rubocop.
Klass.( key_1: 'hello', key_2: 'world' )
$ [bundle exec] rubocop -V 1.5.0 (using Parser 2.7.2.0, rubocop-ast 1.3.0, running on ruby 2.6.6 x86_64-darwin19) - rubocop-performance 1.9.1
The text was updated successfully, but these errors were encountered:
Layout/EmptyLinesAroundArguments
[Fix rubocop#9140] Fix an error for Layout/EmptyLinesAroundArguments
08d623c
Fixes rubocop#9140. This PR fixes an error for `Layout/EmptyLinesAroundArguments` when multiline style argument for method call without selector.
[Fix #9140] Fix an error for Layout/EmptyLinesAroundArguments
0849d36
Fixes #9140. This PR fixes an error for `Layout/EmptyLinesAroundArguments` when multiline style argument for method call without selector.
Successfully merging a pull request may close this issue.
Expected behavior
Expected cops to run without errors being raised
Actual behavior
The following errors occured:
An error occurred while Layout/EmptyLinesAroundArguments cop was inspecting .....
Steps to reproduce the problem
Anywhere I use the call syntax, with the arguments on the next line, I get a hard error for rubocop.
RuboCop version
The text was updated successfully, but these errors were encountered: