-
Notifications
You must be signed in to change notification settings - Fork 86
Upgrade Angular + CLI for example app #8
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
Comments
Hi @smithad15, first thank you for the great product. I've been consuming |
Hey @milocosmopolitan. Thanks for your support of the library and volunteering to help. Supporting lazy loading is definitely on the feature roadmap for v10. Right now, we are going through a phase of technical debt reduction and making it easier for folks like yourself to be able to contribute. At the moment, it would be a bit difficult for you to get onboard unfortunately. I'm hoping to get that resolved soon so that we can ensure the quality and stability of the library going forward. Because of that, we won't be adding new features for awhile as we clean house. Please do keep an eye on the repo and my apologies that I don't have a better answer regarding lazy loading support at this moment. |
Hi @smithad15 makes sense. I was able to resolve route lazyloading issue without making any changes to your actually library. On our project we used to consume the code on example app with |
Glad you were able to figure out a solution around it for now. Would love to see an example repo if you get a chance. While the openness of this library does allow workarounds like you described, I do still have a goal of providing a simpler API for the library so that you don't have to worry as much about the registration details |
#77 refers to this as well. |
The current example app is still running Angular 4 and associated dependencies. This need to be brought up to date.
The text was updated successfully, but these errors were encountered: