-
Notifications
You must be signed in to change notification settings - Fork 659
feat(rome_js_analyze): noParameterProperties
#3874
Conversation
✅ Deploy Preview for docs-rometools ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
The documentation says that this rule is deprecated |
Yes, the rule was replaced by parameter-properties. |
By the way, I tried to implement an action to turn the parameter property into a regular property. However, I encountered an issue: when I mutate a node, I cannot mutate a descendant without invalidating the previous mutation. I have to figure out how to overpass this limitation. |
I have some reservations about this rule, here's my concerns:
|
I think that
I was not aware of this use. It could definitively bring friction.
The arguments I could add:
|
I think the easiest way to implement this without encountering conflicts in the mutation would be to:
|
noParameterProperties
This PR is stale because it has been open 14 days with no activity. |
@Conaclos Do you have a version with the mutation problem so I can look it up? |
@xunilrj I committed my last wip commit. I did not take a look to your proposal yet. |
@xunilrj |
Summary
This implements ESLint's no-parameter-properties.
Test Plan
Unit tests and doc-tests included.