fix(@angular/cli): add a flag to let assets outside of outDir

[hansl]

On top of #7778
Fixes #8122

[filipesilva]

WDYT of having the flag directly on the asset object definition? #8122 (comment)

[filipesilva]

Can you add a test that ensures this works?

[filipesilva]

Docs should also be added in https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/asset-configuration.md

[hansl]

@filipesilva PTAL.

[dzonatan]

So the whole project cannot be built outside anymore (using ../ in apps outDir)?
That's a breaking change. :/ At least add a note in release logs.

[BnSmth]

@dzonatan, The change you are referring to occurred in #7778. This change adds a flag to .angular-cli.json to allow the original behavior (allowing assets to be output outside outDir).

[dzonatan]

@BnSmth, I'm not talking about assets. Instead about entire application. That change in #7778 only checks the asset paths against outDir. There is no limitation to use ../ in outDir.

Simple steps to reproduce:

1. ng new example
2. add ../ for apps[0].outDir in .angular-cli.json
3. ng build

Do that with both cli versions and you will see in 1.5.3 it builds and in 1.5.4 doesn't.

If this was not intentional then I'll create an issue.

[guilhermejcgois]

@dzonatan I have created one #8613, this change caught us by surprise 😢

[BnSmth]

@dzonatan Sorry, my bad. I misunderstood the issue and agree that a fix needs to be put in place. Also, as you said, given this is a breaking change, a note should have been added to the release.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}