Skip to content

ng-promote / ng-export #357

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

Closed
zackarychapple opened this issue Mar 28, 2016 · 2 comments
Closed

ng-promote / ng-export #357

zackarychapple opened this issue Mar 28, 2016 · 2 comments
Labels
effort3: hard (weeks/months) feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@zackarychapple
Copy link
Contributor

ng-promote:
As components are more widely used in an application there should be a way to promote them via the CLI however once they reach the top level of the app the next promotion step should be an extraction to its own published npm module.

ng-export / ng-import:
As code re-use increases there becomes a need to export and import configurations. With the ability to generate entire cli projects from a meta json object we should also be able to export / import routes and all their child components. As we are generating the application we should be keeping track of whats generated in a meta json for the project.

@zackarychapple zackarychapple added the feature Issue that requests a new feature label Mar 28, 2016
@filipesilva filipesilva added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent effort3: hard (weeks/months) labels Jun 4, 2016
@hansl hansl modified the milestone: RC1 Nov 11, 2016
@hansl
Copy link
Contributor

hansl commented Dec 5, 2016

Closing this. This will not be done before we move to having a proper static analyzer and toolkit, so post final.

@hansl hansl closed this as completed Dec 5, 2016
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort3: hard (weeks/months) feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

3 participants