Add code reuse FAQ to NG Module Guide#17129
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.
|
|
I signed it! |
|
CLAs look good, thanks! |
|
If PR #16486 is merged, then this PR will not be necessary. |
|
|
||
| ## How do I reuse Angular Modules in other projects? | ||
|
|
||
| Currently there is no official way to package Angular Modules for resuse. Follow [this issue](https://github.com/angular/angular-cli/issues/6510) for updates. |
|
@rjsteinert I'm closing this because we plan to improve the docs (and the CI is red and there are 2 commits) Thanks for your feedback |
|
Got it. I see the CI feedback now... And I'll rebase master in the future so there aren't merge commits. |
|
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. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
Folks expect that there is standard tooling for sharing Angular Modules.
What is the new behavior?
There is not standard tooling for sharing Angular Modules.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
Related issue: angular/angular-cli#6510
Which is a continuation of this heated issue: angular/angular-cli#1692