Extending lazy-load functionality to include loading standalone components for specific routes. #995
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d added the loadComponent property.
…t changes to angular framework.
…PI with newest angular API. inputs signals now work for view bound components.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, This is a work in progress that I will like to present to you. It covers 3 significant changes, most of them related to the lazy-load functionality.
loadNgModuleand the related functionality to stop using@deprecatedAngular APIs.loadComponent, and related functionality to lazy-load standalone components.ui-viewcomponent to replace@deprecatedAngular APIs. The APIs changes are significant as this update will make components rendered using ui-view work well with the newer input Signals.Please let me know any feedback regarding this changes,
Thanks you all.