Fix synthetic properties in hasExcessProperties#16377
Merged
Merged
Conversation
Previously it would crash if valueDeclaration was not set
mhegazy
approved these changes
Jun 8, 2017
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.
3 participants
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.
hasExcessPropertynow only usesvalueDeclarationfor error reporting if available. Previously it would crash ifvalueDeclarationwas not set; this happened with synthetic property symbols, specifically those created bygetSpreadType.getSpreadTypecreates synthetic properties to removereadonlyand to create union types when spreading an optional property into another property.Fixes #16292