Make "app" point configurable in component generation - #3878

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

CLAs look good, thanks!

You're trying to make src/app be src/{ngConfig.app[0].app} ?

Correct. This would make the "app" point configurable. When attempting to build a generic module in parallel with an specific application, this type of structure makes it easier to keep them separate.

Superseded by #4610 I think.

@filipesilva I do not think it is infact superceded by #4610, I think they're the similar and parts of a whole.

ng new command creates the project with src/app. Once that's done and #4610 is merged, identifying the "mount-ish" point is irrelevant.

Adding a flag for ng new might be beneficial but is outside the scope of where this PR went.

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.}