Make advanced Signals + RxJS state management easier WITH this new API 

New newsletter goes out tomorrow: mobirony.ck.page/4a331b9076 - I've got a back log of cool Angular things around the web to share this week

Thank you for this inspiring video. I think the code looks very clean! The only thing that concerns me a bit is that it's not fully typesafe so I would probably try to come of with a similar but typesafe solution. But again, cool video!👍

What the heck is ngxtension? Everything gets so complicated :( I just wanna be cool, but i can't understand anything

Great content as usual. I hope this will stabilize so that best practices with signals can be unified.

Is this implementation typesafe? Like does it check if the type of the reducer arg is compatible with the observable source?

@JoshuaMorony I have been using rx angular with rx state which solves all these in same way long before signals. have a look at that

Omg, there are 200+ functions in the rxjs library, why add more?

Iguess it is more convenient to use ngrx/component-store for it. Or rx-angular lib. I know that you used it and maybe you can provide your thoughts how to realize it with component-store? Also it is very interesting how you can combine it with your original architecture and folder. Thanks a lot for your videos! It is really helpful

Hi, I was playing with your recommandation for the state management and declarative programming. (I have completed your course). I was wondering what would be your approach for a specific scenario. I have built a task management system, where I have lists panel shows all the lists and a label of how many incomplete tasks. When clicking on the list then I show the list of tasks belongs to that list. I have one smart component: UI components: 1. Lists 2. Lists Item I have two services one for the list and one for the task items. The issue is that I would like declarative when I check to complete or incomplete a task to change the number of incomplete tasks on the list panel. I have done it, but I would love to get your recommendation here

Doesn't that open you up to where the actual value of the signal is in a state that is impossible to be derived from the observable(s)? This feels like it violates 'purity' as you now have all kinds of 'out of band' updates that can happen to the value.

Putting aside CD issues for now, it seems like signals are an easy onramp for junior devs, and nothing more. We're spending a lot of energy to put signal's imperative dangers back into a declarative box. We might better spend our time learning declarative streams/state (rxjs) in our teams and master one tech rather than onboarding more. Regardless, thanks for your efforts here Joshua!

1:17 The guy who lectured out about declarative code in just about every video is suddenly "OK" with having an unknown number sources of truth for a state. I don't get what is the advantage of connect. Would be much better to use "toSignal" in the regular case, and build some other kind of utility to CREATE a new signal declaratively from various "action" observables + reducers.

does this really need this much complexity. Frameworks should make things simplier.

Joshua to the rescue, making things even more complicated and meandering.

Why ngextension when we have rxState

your error$ stream is not working and not update state.... it is working if catchError put in connect...it is fail working, morony

So angular is becoming the most annoying framework in a js world: redux pattern, BUT with signal & observable. omfg. I already regret angular < 16.