fix(react): honor JSX pragma in display-name - #2095
Merged
Merged
Conversation
2 tasks done
elecmonkey
marked this pull request as draft
September 7, 2026 10:58
elecmonkey
marked this pull request as ready for review
September 7, 2026 11:01
fansenze
approved these changes
Sep 7, 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.
Summary
Make
react/display-nameresolve the React pragma from source@jsxcomments before falling back to settings, matching eslint-plugin-react v7.37.5.Restore the skipped upstream case and add 12 regression scenarios covering pragma precedence, fallback, and wrapper substitution in both source-only and checker-backed Programs.
Validation
display_nameandreactutil.display-nameJS integration tests passed.Checklist