angular: remove deprecated use of ComponentFactoryResolver - #2566
Merged
lucas-koehler merged 1 commit intoMay 5, 2026
Merged
Conversation
- Replaced by using ViewContainerRef.createComponent directly with a component. - Enables compatibility with Angular 22 which removes API access to ComponentFactoryResolver
✅ Deploy Preview for jsonforms-examples ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
coverage: 82.957%. remained the same — lk/angular/remove-deprecated-ComponentFactoryResolver-use into master |
Member
|
Works for me! |
sdirix
approved these changes
May 4, 2026
lucas-koehler
deleted the
lk/angular/remove-deprecated-ComponentFactoryResolver-use
branch
May 5, 2026 07:00
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Uh oh!
There was an error while loading. Please reload this page.