Deemphasize old JSX transform#61586
Merged
RyanCavanaugh merged 1 commit intomicrosoft:mainfrom Apr 17, 2025
Merged
Conversation
ee8452f to
5b0dfd9
Compare
5b0dfd9 to
2fb9a19
Compare
Member
|
I feel like this is fine, though I suspect there are other places where we order the message the other way around? |
Contributor
Author
|
I couldn't find any when looking for |
RyanCavanaugh
approved these changes
Apr 17, 2025
Contributor
Perhaps, the schema of |
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.
People should choose the new, automatic transform
over the old transform which required a React import.
Test plan
Applied changes to local
tsccode and ranpnpm tsc test.tsx --jsx:Fixes #61585
Related:
compilerOptions.jsxto reflect latest preferences TypeScript-Website#2994