feat(enforce-store-naming-convention)!: enforce in binding contexts#181
Merged
Conversation
✅ Deploy Preview for eslint-plugin ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
kireevmp
force-pushed
the
feat/store-naming-destructuring
branch
from
201e519 to
10f030a
Compare
AlexandrHoroshih
approved these changes
Apr 21, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following in steps of #171, this PR upgrades
enforce-store-naming-conventionto detect identifiers in binding contexts and report violations there as well. This should now include almost every context where developer can control the naming of the identifier – object & array destructuring, assignment patterns and function parameters.As a bonus, the rule explicitly no longer provides the suggestion for identifiers with type annotations – previously these "fixes" erased the type annotation if it was present, deleting developer's code.