fix: parse export type *#358
Open
gthb wants to merge 4 commits into
Open
Conversation
Add test cases for tree-sitter#348: - `export type * from '...'` - `export type * as Name from '...'` These are valid TypeScript (since 3.8) but currently produce ERROR nodes.
Add `*` and `* as Name` cases to the `export type` branch. Fixes tree-sitter#348
Cover more `namespace_export` forms: - `export type * as default from './module'` - `export type * as "string-name" from './module'`
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Support
export type *andexport type * as XWhy
Fixes #348 — current grammar only accepts
export type { ... }andexport { type ... }and yields ERROR nodes for the above.Also
Add test cases for
export { type X }andexport { type X as Y }These were already supported, but AFAICT not covered in any test.