This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
feat(rome_js_analyze): noParameterAssign
#4264
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-rometools ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
Conaclos
changed the title
noParameterAssign
denbezrukov
approved these changes
Mar 7, 2023
ematipico
pushed a commit
that referenced
this pull request
Mar 10, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements no-param-reassign.
In contrast to the ESLint rule, this rule cannot be configured to report assignments to a property of a parameter.
I think this kind of check should be implemented in other rule (if we need to report this kind of mutations).
Test Plan
ESLint tests included.
Documentation
Included.