Fix #343: Support type params in CallExpression, NewExpression (TS) #358
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
jgoz
force-pushed
the
callexpression-type-arguments
branch
from
418ed38 to
d532dea
Compare
Already supported in Flow. Fixes benjamn#343
jgoz
force-pushed
the
callexpression-type-arguments
branch
from
d532dea to
63d9b98
Compare
Author
|
@benjamn Any chance you could take a look at this? I've rebased my original changes on the latest master and it fixes the linked issue. |
jgoz
changed the title
Author
|
I also switched to using the |
|
I know this is a bit old, but any chance this could be merged to unblock this related jscodeshift ticket? facebook/jscodeshift#389 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes #343.
It looks like this is already supported in Flow (tests).