Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no-get-properties rule extended to invalid non-destructive assignment. #419

Closed

Conversation

pavlikmarek
Copy link

extending by: #415

@bmish
Copy link
Member

bmish commented May 8, 2019

Is there any reason for this rule to be limited to assignments still? Should we expand it to all CallExpression usages of getProperties? That would match the behavior of the no-get rule.

@pavlikmarek
Copy link
Author

pavlikmarek commented May 10, 2019

@bmish Agree that there is no reason to leave limitation to assignments. Fixed.

@bmish
Copy link
Member

bmish commented May 10, 2019

Given that this rule is now almost identical to no-get, how about we delete this rule and simply update no-get to catch both get and getProperties? I'm assuming anyone wanting to ban one would want to ban both. Seems overkill to have two separate rules now.

@bmish
Copy link
Member

bmish commented May 15, 2019

@pavlikmarek I went ahead and took care of the rule consolidation in #421. You can close this PR. Thanks for helping us improve these rules!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants