Fix parsing of methods and fields named "declare" #575
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 #545
When originally porting babel/babel#11146, there was a
mistake where we were using
eatContextual
when actually it was important touse
tsParseModifier
, sincetsParseModifier
won't eat a name token if thefollowing token indicates that it must be the name of a method or field. This PR
fixes that by switching to
tsParseModifier
as Babel does.It might be good to later refactor/simplify
tsParseModifier
if the keywordspecificity is just for error handling (and to maybe avoid the
snapshot/restore), but that can be a follow-up.