Add tests for elide imports and fix named imports with default imports #13243
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.
This also adds the option to provide addition files when using
createTypescriptContext
this is paramount for the elide imports tests as without this certain symbols won't have the full details.Which will cause tests to be false positive and re-surface issues like #13212
… named imports
At the moment when having a default import together with a named import example:
And the default import becomes unused it will drop the entire node which will caused used named imports to be dropped as well.
getExportSpecifierLocalTargetSymbol
andgetShorthandAssignmentValueSymbol
to handle symbols lookupsUse typechecker methods to handle special cases for
ExportSpecifier
andShorthandPropertyAssignment