Rename RubocopChecker to LinterWorker or similar
Open
Nobody has claimed this yet.
enhancement
help wanted
pinned
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
RubocopChecker doesn't just do rubocop anymore and it's confusing. If we start adding enable/disable for specific linters as per #244 , then the naming is going to get more confusing.
Contributor guide
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
Locate the RubocopChecker class and all references to it, then review the naming context alongside issue #244. Rename the worker to a name that reflects its broader linter responsibilities and update its references; done when the project no longer uses the confusing RubocopChecker name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100