-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grammar error on export type *
#37064
Conversation
@typescript-bot cherry-pick this to release-3.8 |
Heya @DanielRosenwasser, I've started to run the task to cherry-pick this into |
Hey @DanielRosenwasser, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-3.8 manually. |
Did I mess that up by merging it? @typescript-bot cherry-pick this into release-3.8 |
Heya @andrewbranch, I've started to run the task to cherry-pick this into |
Hey @andrewbranch, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-3.8 manually. |
* Fix renaming an ExportSpecifier name when propertyName is present (#36790) * Fix renaming exportSpecifier name when propertyName is present * Add baseline test for name without propertyName too * Set correct pos for NamespaceExport (#36794) * Set correct pos for NamespaceExport * Update tests * Cherry-pick PR #37064 into release-3.8
Fixes #36966
The first commit added the missing calls to
markSymbolOfAliasDeclarationIfTypeOnly
so as to recognizeexport type *
forms as type-only while simultaneously disallowing it with a grammar error. Mostly I was curious how close we were to supportingexport type *
, and it appears that it’s only a couple extra lines. Afterwards, I reverted the extra calls because it created two errors where one would suffice.