Type lookup in getIntrinsicAttributestypeFromJsxOpeningLikeElement should match getIntrinsicTagSymbol #42819
Conversation
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
…ould match getIntrinsicTagSymbol
typescript-bot
added
Author: Team
For Milestone Bug
sandersn
approved these changes
Feb 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(
getDeclaredTypeOfSymboldoes not do what we want on type aliases.)Additionally, removes the assertion and conservatively adds an
|| errorTypeto satisfy the typechecker instead (while so long as the lookups methods match betweengetIntrinsicAttributestypeFromJsxOpeningLikeElementandgetIntrinsicTagSymbol, it should never beundefined, if they ever drift again, returning theerrorTypehere is better for follow-on issues than quietly leakingundefined).Fixes #42753