-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
fix(router): Remove deprecated ComponentFactoryResolver from APIs #49239
fix(router): Remove deprecated ComponentFactoryResolver from APIs #49239
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great cleanup 👍
nit: You could also remove the line in the depreciation guide ! |
1a72197
to
285a505
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed-for: public-api
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Reviewed-for: public-api
BREAKING CHANGE: `ComponentFactoryResolver` has been removed from Router APIs. Component factories are not required to create an instance of a component dynamically. Passing a factory resolver via resolver argument is no longer needed and code can instead use `ViewContainerRef.createComponent` without the factory resolver.
This commit removes the deprecation notes from the deprecations guide for APIs that have been removed.
285a505
to
c824e8a
Compare
This PR was merged into the repository by commit ed110a0. |
This commit removes the deprecation notes from the deprecations guide for APIs that have been removed. PR Close #49239
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. |
BREAKING CHANGE:
ComponentFactoryResolver
has been removed from Router APIs. Component factories are not required to create an instance of a component dynamically. Passing a factory resolver via resolver argument is no longer needed and code can instead useViewContainerRef.createComponent
without the factory resolver.