[Proposal] Enabling `no-param-reassign` eslint rule
Open
Nobody has claimed this yet.
never-stale
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
I've personally often feel frustrated due to being extremely hard to track an implementation after a reassignment of parameters, due to the ambiguity of types in a function that has a JSDoc declaration.
I recommend enabling https://eslint.org/docs/latest/rules/no-param-reassign. There is currently ✖ 1597 problems (1597 errors, 0 warnings).
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
Start by reviewing the proposed ESLint no-param-reassign rule and running the repository's existing ESLint checks. The current lint run reports 1,597 errors; done means the rule is enabled and those parameter-reassignment violations are resolved without introducing new lint errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100