allow jsx identifiers to start with keywords #4705
Merged
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
| @@ -12,6 +12,10 @@ namespace ts { | |||
| export function createNode(kind: SyntaxKind): Node { | |||
| return new (getNodeConstructor(kind))(); | |||
| } | |||
|
|
|||
| export function tokenIsIdentifierOrKeyword(token: SyntaxKind): boolean { | |||
There was a problem hiding this comment.
This should be exported from the scanner (and marked internal).
|
Can you add an example of the property being a keyword entirely? Like |
|
👍 i would merge this into master and not release-1.6 |
vladima
added a commit
that referenced
this pull request
Sep 10, 2015
allow jsx identifiers to start with keywords
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #4644