fix: Add type-annotations support to react/sort-comp #3110
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
anandfresh
approved these changes
Apr 30, 2025
|
@dcq01 please don't do this - it's a form of spam, and LLMs aren't capable of producing anything valuable here, in addition to the legal provenance of their output being unclear. |
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.
Closes #1922
Currently, react/sort-comp does not support type-annotations, which causes inconsistencies in projects using Flow or TypeScript. Adding this support aligns better with modern React development practices.
This PR adds support for type-annotations in the react/sort-comp ESLint rule. This is particularly useful for projects using Flow and TypeScript, allowing developers to maintain a consistent order for type annotations like props, state, and context.