Handle resolving and unknown symbols in getLiteralTypeFromPropertyName#22406
Merged
weswigham merged 1 commit intoMar 8, 2018
microsoft:mastermicrosoft/TypeScript:masterfrom
weswigham:resolving-unknown-symbolsweswigham/TypeScript:resolving-unknown-symbolsCopy head branch name to clipboard
Merged
Handle resolving and unknown symbols in getLiteralTypeFromPropertyName#22406weswigham merged 1 commit intomicrosoft:mastermicrosoft/TypeScript:masterfrom weswigham:resolving-unknown-symbolsweswigham/TypeScript:resolving-unknown-symbolsCopy head branch name to clipboard
weswigham merged 1 commit into
microsoft:mastermicrosoft/TypeScript:masterfrom
weswigham:resolving-unknown-symbolsweswigham/TypeScript:resolving-unknown-symbolsCopy head branch name to clipboard
Conversation
ghost
approved these changes
Mar 8, 2018
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.
1 participant
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.
These are set to be a symbol's target when an alias can't be resolved or is resolving, and, ofc, have differing names than the symbol targeting them (meaning there can't be a cached name on the target anyway, since the symbol is shared across many possible names).
Fixes #22403