-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Fix JSX inference with excess properties #53810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix JSX inference with excess properties #53810
Conversation
790002e to
af288ac
Compare
jakebailey
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels accurate but @weswigham probably knows better
|
@jakebailey any chance of landing this into the just started 5.2? :) |
|
This PR is 100 commits behind main at this point, but let me close/reopen just to recheck CI. That and @typescript-bot test this |
|
Heya @jakebailey, I've started to run the diff-based top-repos suite on this PR at 98d4243. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the abridged perf test suite on this PR at 98d4243. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the diff-based user code test suite on this PR at 98d4243. You can monitor the build here. Update: The results are in! |
|
Heya @jakebailey, I've started to run the extended test suite on this PR at 98d4243. You can monitor the build here. |
|
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at 98d4243. You can monitor the build here. Update: The results are in! |
|
@jakebailey Here they are:Comparison Report - main..53810
System
Hosts
Scenarios
Developer Information: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@jakebailey Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Everything looks good! |
|
@jakebailey Here are the results of running the top-repos suite comparing Everything looks good! |
|
Hey @jakebailey, the results of running the DT tests are ready. |
|
FWIW back when I reviewed this last month, I did go do the git history checking to verify, and it is effectively the same fix and the new flag that's used instead now (compared to that old PR) would have been updated too, so, this to me seems sound (but I've already said that). |
fixes #53789
it's basically the same fix as the one here, just applied to JSX