Skip to content

fix(angular): use Angular signals directly#1733

Open
crisbeto wants to merge 1 commit into
a2ui-project:mainfrom
crisbeto:ng-signals
Open

fix(angular): use Angular signals directly#1733
crisbeto wants to merge 1 commit into
a2ui-project:mainfrom
crisbeto:ng-signals

Conversation

@crisbeto

Copy link
Copy Markdown
Collaborator

Reworks the Angular renderer to use Angular signals directly based on the APIs from #1714, instead of having to bridge Angular and Preact signals.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request migrates the Angular renderer from using bridged Preact signals to natively using Angular signals, removing the @preact/signals-core dependency and updating services and tests accordingly. The review feedback highlights a critical issue in initializeAngularReactivity where multiple active EnvironmentInjector instances can interfere with each other's lifecycles, potentially resetting the signal implementation prematurely or throwing errors. A stack-based approach is suggested to safely track and clean up active injectors.

Comment thread renderers/angular/src/v0_9/core/reactivity.ts
Reworks the Angular renderer to use Angular signals directly based on the APIs from a2ui-project#1714, instead of having to bridge Angular and Preact signals.
@crisbeto crisbeto requested a review from josemontespg June 23, 2026 10:14
@crisbeto crisbeto marked this pull request as ready for review June 23, 2026 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant