fix(misc): handle moving to a subfolder which results in the same project name and normalize import path #6507
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.
Current Behavior
When moving an Angular project to a subfolder which results in the same project name to be generated (e.g. from
my-project
tomy/project
), the module gets incorrectly deleted and the path alias in thetsconfig.base.json
gets changed even though the project name is the same. The latter issue is caused because when moving any project to a nested structure with noimportPath
provided, the auto-generatedimportPath
uses the directory name (with/
) instead of the project name.Expected Behavior
Moving an Angular project should not delete the module file. Moving any project should correctly auto-generate the
importPath
.Related Issue(s)
Fixes #6487