fix: do not use JSX.ElementChildrenAttribute under jsx: react-jsx or jsx: react-jsxdev#60880
Merged
iisaduan merged 3 commits intomicrosoft:mainfrom Jan 24, 2025
Merged
fix: do not use JSX.ElementChildrenAttribute under jsx: react-jsx or jsx: react-jsxdev#60880iisaduan merged 3 commits intomicrosoft:mainfrom
JSX.ElementChildrenAttribute under jsx: react-jsx or jsx: react-jsxdev#60880iisaduan merged 3 commits intomicrosoft:mainfrom
Conversation
Andarist
reviewed
Dec 30, 2024
Contributor
There was a problem hiding this comment.
it might be good to add a test case that defines ElementChildrenAttribute as something different than children to verify that it's ignored in favor of "hard-coded" children
Contributor
Author
There was a problem hiding this comment.
Indeed! Added a test case.
…react-jsx and react-jsxdev
Member
|
@typescript-bot test it |
Collaborator
Collaborator
|
@jakebailey Here are the results of running the user tests with tsc comparing Everything looks good! |
Collaborator
|
Hey @jakebailey, the results of running the DT tests are ready. Everything looks the same! |
Collaborator
|
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Collaborator
|
@jakebailey Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
andrewbranch
approved these changes
Jan 23, 2025
iisaduan
approved these changes
Jan 23, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Happy Holidays! Fixes #60572
🖼️ Background
Under
jsx: react-jsxorjsx: react-jsxdev, the name of the prop for JSX children is alwayschildren. The jsx transformer properly implements this:TypeScript/src/compiler/transformers/jsx.ts
Line 308 in 56a0825
However, the type checker didin't take this into consideration. Instead, it used
JSX.ElementChildrenAttributeto determine the name of prop. If type definition lacks this interface, undesirable compiler errors are emitted (like the one mentioned in the linked issue).It is of note that, I believe, no practical type definition for JSX libraries ever provided such definition that would lead to errors like those.
That said, I think the current behavior is still a bit harmful to those who want to learn how to write type definitions for JSX libraries, so proposing a fix.
🦾 Solution
This PR fixes the
getJsxElementChildrenPropertyNamefunction so thatchildrenis hard-coded under thesejsxmodes.🌵 Current Behavior
code:
Errors:
✨ New Behavior
(No error)