rubocop / rubocop/ruby-style-guide
Enforce no parentheses for `include`, `extend`, etc?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 16.5k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/shopify/ruby-style-guide#syntax we say:
omit parentheses when the invocation is single-line and the method [...] is a class method call with implicit receiver.
But currently this isn't enforced by RuboCop.
The relevant cop is probably https://www.rubydoc.info/gems/rubocop/1.43.0/RuboCop/Cop/Style/MethodCallWithArgsParentheses
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the syntax section of the Ruby Style Guide and the referenced RuboCop::Cop::Style::MethodCallWithArgsParentheses documentation. Determine how the stated rule should apply to include, extend, and similar calls; the work is done when RuboCop enforces the agreed cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100