Don't retarget dependencies if a symbol is imported multiple times with different local names #8738
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.
Closes #8705
can cause a situation where it tried to rewrite a dependency to have these symbols (so saying that in the parent asset, import
x
and make it available as$id$re_export$x
and also importx
and make it available as$id$re_export$y
:This seems fine but the way this is achieved in the symbols is that the transformer detects and uses the same local identifier for both. When retargeting dependencies however, the asset symbols cannot be changed so it just has to deopt out of retargeting here.