Skip to content
New issue

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

Jump to bottom

Conflicting rules Style/LambdaCall and Style/MethodCallParentheses for .call method without args #2569

Closed
mockdeep opened this issue Jan 1, 2016 · 1 comment
Closed

Conflicting rules Style/LambdaCall and Style/MethodCallParentheses for .call method without args #2569

mockdeep opened this issue Jan 1, 2016 · 1 comment

Comments

@mockdeep
Copy link
Contributor

mockdeep commented Jan 1, 2016

When I have a .call method that takes no arguments, I can't win between 2 rubocop rules. If I do it this way:

thing.call

It complains on the Style/LambdaCall rule, and this way:

thing.()

It complains about Style/MethodCallParentheses. Unfortunately, what rubocop wants in this instance isn't valid ruby syntax:

thing.
@alexdowad
Copy link
Contributor

I have a fix for this. Waiting for my open PR to be merged, then I'll open another one.

@bbatsov bbatsov closed this as completed in ce4f0b5 Jan 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mockdeep @alexdowad