Add fallback error locations for nameless declarations, better class error locations #42585
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
typescript-bot
added
Author: Team
For Milestone Bug
| @@ -161,9 +162,9 @@ namespace ts { | |||
| } | |||
|
|
|||
| function reportPrivateInBaseOfClassExpression(propertyName: string) { | |||
| if (errorNameNode) { | |||
| if (errorNameNode || errorFallbackNode) { | |||
There was a problem hiding this comment.
I'd just capture these into a local so you can avoid the !
sandersn
approved these changes
Feb 5, 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.
These errors were going unreported because we had no location registered to report them on. Now we allow a non-name fallback location for those declaration emit errors which do not require a name. (And, additionally, set the name location when emitting classes).
Fixes #42499