Don’t let other completions shadow type keywords in type locations #48939
Conversation
This file contains 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
typescript-bot
added
Author: Team
For Milestone Bug
sheetalkamat
approved these changes
May 3, 2022
| @@ -164,7 +164,7 @@ namespace ts.Completions { | |||
| TypeAssertionKeywords, | |||
| TypeKeywords, | |||
| TypeKeyword, // Literally just `type` | |||
| Last = TypeKeywords | |||
| Last = TypeKeyword | |||
There was a problem hiding this comment.
😅 oof, who even uses Last?
gabritto
approved these changes
May 4, 2022
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.
Fixes #48075
As part of this fix, I started to implement a lot more keyword filtering than we currently do (type keywords are normally offered in value locations 🤦♂️), but stopped when it became clear that it was going to be a significant change late in the release cycle. I hope to pick that back up for 4.8.