I totally feel you. Using untracked or some wrapper around it like a custom explicitEffects helper or toObservable really helps to see what’s going on and to avoid issues.
Sounds like signals are always a state of data, and it is not possible to make a decision for invoking data change based on data state, the concept of `view = function(state)` is broken in such case. Data could not have an intention to be self changed (via `effect`), because behaviour is not a data or state feature. Behaviour that based on Action/Event is a missing part of signal architecture
Not really. It’s the official ecmascript syntax (es2022) and I decided to use it in this example. Saying this, the TypeScript private also has several benefits: it’s easier to debug (because it’s actually public after transpiling to JavaScript) and it comes with no performance overhead at runtime (for the same reason).
![[EN] New RFC: OAuth 2.x for Browser-based Apps](http://i.ytimg.com/vi/mORR3hpMaJQ/mqdefault.jpg)
![[EN] New RFC: OAuth 2.x for Browser-based Apps](/img/tr.png)
![เขามัทรี - เอ็กซ์ ศุภกฤต - จอนนี่มิวสิค [ Official MV ]](http://i.ytimg.com/vi/AS9ufKuQIVs/mqdefault.jpg)
![[EN] Angular Testing in 2024 - Interview](/img/n.gif)
Angular Architecture Workshop:
www.angulararchitects.io/en/training/advanced-angular-architecture-workshop/
Don’t tell my wife but I seriously love you man! Haha thank you for the content and information
We're here in Styria -> we're distilling everything 🤣🤣🤣
Nice!!
Nice talk as always.
awesome . thank you for sharing
This was great. Love signals, but having to use untracked() heavily lol
I totally feel you. Using untracked or some wrapper around it like a custom explicitEffects helper or toObservable really helps to see what’s going on and to avoid issues.
Sounds like signals are always a state of data, and it is not possible to make a decision for invoking data change based on data state, the concept of `view = function(state)` is broken in such case.
Data could not have an intention to be self changed (via `effect`), because behaviour is not a data or state feature.
Behaviour that based on Action/Event is a missing part of signal architecture
first time I see the injections with # prefix. Is there a convention on why did you write it like that?
Not really. It’s the official ecmascript syntax (es2022) and I decided to use it in this example. Saying this, the TypeScript private also has several benefits: it’s easier to debug (because it’s actually public after transpiling to JavaScript) and it comes with no performance overhead at runtime (for the same reason).
@@ManfredSteyer Thanks for clarification :)