-
Notifications
You must be signed in to change notification settings - Fork 12k
Make "app" point configurable in component generation #3878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
|
CLAs look good, thanks! |
Lint complained about line lengths?
You're trying to make |
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. |
Adding a flag for |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
angular-cli.json allows flexibility for how project structure is defined. This PR allows for the "app" to be configurable. Consider the following tree structure: