And is there something planned regarding the management of suspense states, hence having information regarding loading and error states out of the box? Could something like this be easily built using custom features?
I have the same question. Wondering if there's a way we can defer initialization and hand the signal store an initial state. Otherwise I'd end up with optional properties everywhere which feels wrong.
I might look like dynamic props at first glance. But it's indeed statically typed. The NGRX does a great job telling TypeScript about the Types of all the props you define.
Since the appearance of signals, I feel like the Angular dev team, following the waves of trends, is turning a well-thought-out enterprise-level framework into something React-like and FP-oriented. Big mistake.
Terrific presentation Marko, thank you!
Great video. It would be interesting to see how this examples are tested, though e.g. the Counter Component and the CounterStore.
And is there something planned regarding the management of suspense states, hence having information regarding loading and error states out of the box? Could something like this be easily built using custom features?
I have the same question. Wondering if there's a way we can defer initialization and hand the signal store an initial state. Otherwise I'd end up with optional properties everywhere which feels wrong.
thanks!
sensational stuff
But we definitely don't want to define dynamic class properties or methods. That's why we use a typed language like TS.
I might look like dynamic props at first glance. But it's indeed statically typed. The NGRX does a great job telling TypeScript about the Types of all the props you define.
Since the appearance of signals, I feel like the Angular dev team, following the waves of trends, is turning a well-thought-out enterprise-level framework into something React-like and FP-oriented. Big mistake.
It does not make sense .. signal needs to be more mature.. but thanks for the presentation