-
-
Notifications
You must be signed in to change notification settings - Fork 48
feat: add svelte/prefer-destructured-store-props
rule
#270
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
Conversation
Editor doesn't like this but maybe it's ok?
Also add a description
🦋 Changeset detectedLatest commit: 5de72f9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very thorough, wow. I don't see any red flags.
object: TSESTree.Identifier & { name: string } | ||
} | ||
|
||
const keywords = new Set([ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would something like esutils
be useful here since it's less likely to drift out of sync?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for checking this PR. I think it would be great to replace with esutils as you suggested! I will change this PR.
This PR is a follow up for #208.
Changed the rule to only warn about store property access in templates.
close #208