Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Import/export declarations improperly elided in certain cases #87

Closed
nonara opened this issue Jan 4, 2021 · 0 comments · Fixed by #88
Closed

Import/export declarations improperly elided in certain cases #87

nonara opened this issue Jan 4, 2021 · 0 comments · Fixed by #88

Comments

@nonara
Copy link
Collaborator

nonara commented Jan 4, 2021

Some import and export declarations get improperly elided.

Example:

export * as name from 'module'

The elision logic should be updated to only process if named bindings are present in the import / export clause
@nonara nonara changed the title Export * improperly elided Import/export declarations improperly elided in certain cases Jan 4, 2021
nonara added a commit that referenced this issue Jan 4, 2021
@nonara
fix: Certain edge cases existed where type elision improperly elided …
0befbe5 
…full import / export declarations without named bindings (closes #87)
@nonara nonara mentioned this issue Jan 4, 2021
Merged
@nonara nonara closed this as completed in #88 Jan 4, 2021
nonara added a commit that referenced this issue Jan 4, 2021
@nonara
fix: Certain edge cases existed where type elision improperly elided …
84a7866 
…full import / export declarations without named bindings (closes #87)
@nonara nonara mentioned this issue Feb 19, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

2.2.0 LeDDGroup/typescript-transform-paths
1 participant
@nonara