This repository was archived by the owner on Apr 4, 2025. It is now read-only.
fix(@schematics/angular): use old config root to set root and sourceR… #985
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
…oot during update-6
Within the update-6 migration, the
rootandsourceRootare both hard coded. The previousapp.rootshould be used. Similarly, the e2e project'srootandsourceRootwere both set to theproject.root.I made an assumption that the
sourceRootof the e2e project would be in a directory under therootcallede2e. I'm not sure if that's a valid assumption but it seems more accurate than a hardcoded''and there is not much of a definite indicator.Fixes angular/angular-cli#10883