Pawel Kozlowski dcf18dc74c fix(core): allow toSignal calls in reactive context (#51831) ... This PR moves the Observable subscription of toSignal outside of the reactive context. As the result the toSignal calls are allowed in the computed, effect and all other reactive consumers. This is based on the reasoning that we already allow signals creation in a reactive context. Plus a similar change was done to the async pipe in the https://github.com/angular/angular/pull/50522 Fixes #51027 PR Close #51831		2023-09-22 09:47:19 -07:00
..
BUILD.bazel	refactor(core): prototype of signals, a reactive primitive for Angular (#49091)	2023-02-21 14:13:08 -08:00
computed_spec.ts	fix(core): allow toSignal calls in reactive context (#51831)	2023-09-22 09:47:19 -07:00
effect_util.ts	refactor(core): switch signals to a refcounting algorithm (#51226)	2023-09-01 14:18:41 +00:00
glitch_free_spec.ts	refactor(core): prototype of signals, a reactive primitive for Angular (#49091)	2023-02-21 14:13:08 -08:00
is_signal_spec.ts	fix(core): allow passing value of any type to isSignal function (#50035)	2023-05-16 09:22:05 -07:00
non_reactive_spec.ts	refactor(core): move effect to render3 and add DestroyRef integration (#49529)	2023-03-28 18:47:58 -07:00
signal_spec.ts	test(core): correct typo in signal_spec.ts (#50392)	2023-05-23 14:11:03 +00:00
watch_spec.ts	refactor(core): make sure that destroyed watch nodes dont run again (#51757)	2023-09-15 14:00:32 +02:00