Uh oh!
There was an error while loading. Please reload this page.
JSX namespace names should not be considered expressions - #54104
Conversation
Wesley Wigham (weswigham)
commented
May 2, 2023
TypeScript Bot (@typescript-bot) test this |
Heya Wesley Wigham (@weswigham), I've started to run the parallelized Definitely Typed test suite on this PR at b22a671. You can monitor the build here. Update: The results are in! |
Heya Wesley Wigham (@weswigham), I've started to run the diff-based top-repos suite on this PR at b22a671. You can monitor the build here. Update: The results are in! |
Heya Wesley Wigham (@weswigham), I've started to run the extended test suite on this PR at b22a671. You can monitor the build here. |
Heya Wesley Wigham (@weswigham), I've started to run the perf test suite on this PR at b22a671. You can monitor the build here. Update: The results are in! |
Good point - let's try that out in a follow-up PR on the top 100. |
Daniel Rosenwasser (DanielRosenwasser)
left a comment
There was a problem hiding this comment.
Looks good but get another review.
Also, might be good to have a test with an index signature like `ns:do-${string}`
TypeScript Bot (typescript-bot)
commented
May 2, 2023
Wesley Wigham (@weswigham) Here they are:CompilerComparison Report - main..54104
System
Hosts
Scenarios
TSServerComparison Report - main..54104
System
Hosts
Scenarios
StartupComparison Report - main..54104
System
Hosts
Scenarios
Developer Information: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TypeScript Bot (typescript-bot)
commented
May 2, 2023
Wesley Wigham (@weswigham) Here are the results of running the top-repos suite comparing Everything looks good! |
TypeScript Bot (typescript-bot)
commented
May 2, 2023
Hey Wesley Wigham (@weswigham), the results of running the DT tests are ready. |
Andrew Branch (andrewbranch)
commented
May 2, 2023
Perf run almost looks like this is visible in parse time, but it’s pretty noisy, and the only real addition is a |
TypeScript Bot (@typescript-bot) perf test this faster |
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to run the abridged perf test suite on this PR at b22a671. You can monitor the build here. Update: The results are in! |
TypeScript Bot (typescript-bot)
commented
May 2, 2023
Daniel Rosenwasser (@DanielRosenwasser) Here they are:Comparison Report - main..54104
System
Hosts
Scenarios
Developer Information: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fixes the regression in this comment, which was regressed by #47356 (and followup #53799), which mistakenly classified
JsxNamespacedNamenodes asExpressions, which masked a ton of locations where they were effectively unhandled - the relevant location in the case of the regression beinggetLiteralTypeFromPropertyName, which started returningerrorTypefor all jsx namespace names (which perviously were correctly thea:bstring, thanks to the funky identifier we used to use).As an aside,
checkExpressionWorkercurrently silently returnserrorTypefor all unknown expression types - shouldn't this be a hardDebug.failcalling out the unhandled case? This may have been more obvious had that been the case.