fix(editor): don't create a duplicate import for aliased files #6062
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.
Problem:
Currently when trying to import the same component from an import source that is aliased in the file, we incorrectly recognize it as a different source and create a duplicate import
Fix:
Take the alias mapping into consideration. The heavy lifting was done in the previous prep PR which was to pass this mapping into the
mergeImports
function.To reproduce/test:
In our sample store project, locate the
Grid
with the sixProductCard
s, and try to move (simply move) one of theProductCard
inside that grid. It used to create a duplicate import.Manual Tests:
I hereby swear that:
Fixes #5980