feat: forbid-component-props, closes #1155
#1167
Merged
Conversation
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
|
@reteps is attempting to deploy a commit to the Rel1cx's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Rel1cx
reviewed
Aug 12, 2025
packages/plugins/eslint-plugin-react-x/src/rules/no-forbidden-props.ts
Outdated
Show resolved
Hide resolved
|
LGTM. |
|
You can try this rule now in version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
This rule adds support for banning certain component properties. This is useful for our project, which uses
preact, and so we discourage the use ofclassName. In addition, we discourage the usage ofsnake_casevariables. This PR adds the ability to lint those errors. This rule was partially written with Cursor. Closes #1155Does this PR introduce a breaking change?
Checklist
fix: remove a typo, closes #___, #___)Other information