You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, this might just be a small edge case and maybe not even desired layout according to the style guide, but if so it should be handled by another cop and not this one.
Initial setup
# Have a method definition with a keyword parameter, where you put the # default value on the next line, followed by another keyword and default# value pair, or a double asterisk.deffoo(bar:
'baz', **
)end
As I said, this might not be a perfect layout in tune with the style guide, but right now there is nothing I found, that forbids this.
Expected behavior
Rubocop should keep the closing parenthesis at exactly this indent and not complain.
That actually is the case, if you move the double asterisk or key-value-pair to a line on their own.
Actual behavior
Rubocop wants to indent the closing parenthesis one further, on the same column as the "bar" symbol in the example.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!
Hi, this might just be a small edge case and maybe not even desired layout according to the style guide, but if so it should be handled by another cop and not this one.
Initial setup
As I said, this might not be a perfect layout in tune with the style guide, but right now there is nothing I found, that forbids this.
Expected behavior
Rubocop should keep the closing parenthesis at exactly this indent and not complain.
That actually is the case, if you move the double asterisk or key-value-pair to a line on their own.
Actual behavior
Rubocop wants to indent the closing parenthesis one further, on the same column as the "bar" symbol in the example.
Steps to reproduce the problem
See the initial setup.
RuboCop version
The text was updated successfully, but these errors were encountered: