Conversation
There was a problem hiding this comment.
I can imagine this being inside the ImportManager as well.
There was a problem hiding this comment.
Haha, I was thinking this logic feels more specific to the schematic portion 😄
There was a problem hiding this comment.
It might make sense to have this in the ImportManager too, but it's also fairly basic.
There was a problem hiding this comment.
Agreed. Maybe it can be a set of common helpers in the import manager directory.
There was a problem hiding this comment.
Haha, I was thinking this logic feels more specific to the schematic portion 😄
There was a problem hiding this comment.
Agreed. Maybe it can be a set of common helpers in the import manager directory.
ebb7058 to
39bde3b
Compare
Updates the import manager to allow for a specific alias to be passed in. This is a prerequisite for switching schematics to the new import manager. Note that passing in an alias disables identifier conflict resolution in order to avoid rewriting the alias that was passed in explicitly. For now this is fine since we have a very narrow use case for it, but we may want to revisit it in the future.
Fixes that the `ImportManager` wasn't picking up some of its configuration options.
Updates the schematics to reuse the common `ImportManager`, instead of having to maintain a separate one.
39bde3b to
4d7bf17
Compare
|
This PR was merged into the repository by commit bb977e0. The changes were merged into the following branches: main |
Updates the schematics to reuse the common `ImportManager`, instead of having to maintain a separate one. PR Close #57096
…ar#57096) Updates the import manager to allow for a specific alias to be passed in. This is a prerequisite for switching schematics to the new import manager. Note that passing in an alias disables identifier conflict resolution in order to avoid rewriting the alias that was passed in explicitly. For now this is fine since we have a very narrow use case for it, but we may want to revisit it in the future. PR Close angular#57096
…ngular#57096) Fixes that the `ImportManager` wasn't picking up some of its configuration options. PR Close angular#57096
…ar#57096) Updates the schematics to reuse the common `ImportManager`, instead of having to maintain a separate one. PR Close angular#57096
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Includes the following changes which allow us to delete one import manager implementation in favor of a common one.
refactor(compiler-cli): add alias option to the import manager
Updates the import manager to allow for a specific alias to be passed in. This is a prerequisite for switching schematics to the new import manager.
Note that passing in an alias disables identifier conflict resolution in order to avoid rewriting the alias that was passed in explicitly. For now this is fine since we have a very narrow use case for it, but we may want to revisit it in the future.
refactor(compiler-cli): import manager not picking up some options
Fixes that the
ImportManagerwasn't picking up some of its configuration options.refactor(migrations): use common import manager for schematics
Updates the schematics to reuse the common
ImportManager, instead of having to maintain a separate one.