fix(@angular/cli): flatten index.html config during output #7314
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.
We're attempting to re-use common library code within the same CLI codebase. To achieve this we're putting apps in separate folders like:
index.html has it's own brand specific things, like a unique
<title>
for instance. This means we need to separate them and point to them using appConfig like:When you run an
ng build
though, the index.html is still inside the branded folder, referencing JS that is up a directory. This PR flattens theappConfig.index
property, as it should always be in the root directory with the JS files anywayFixes: #7309