fix(angular): update import paths relative to app config file location in migration extracting the config #16863
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
The migration extracting the standalone config from the
bootstrapApplication
call into a separate file doesn't rewrite the relative import paths considering the new file location.Expected Behavior
The migration extracting the standalone config from the
bootstrapApplication
call into a separate file should rewrite the relative import paths as needed based on the new file location.Related Issue(s)
Fixes #16849