rubocop / rubocop/ruby-style-guide
Recommend calling super in initialize
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
Many users forget to call super from initialize, which can lead to tricky bugs if the superclass needs to initialize its own state.
Perhaps this should be in the style guide?
I'm not sure if it should be a hard failure, since classes that extend Object or BasicObject or a few other core types don't technically need to invoke super, but the safest pattern would be to always do so.
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 by reviewing the style guide's existing guidance around initialize and inheritance, then compare the behavior of subclasses of Object, BasicObject, and other core types. Decide whether the guide should recommend calling super universally or document exceptions, and update the guidance so the recommendation and its rationale are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100