Angular developers have waited 7 years for better integration with RxJS, but this doesn't seem to be happening. This made me angry at first, but after a lot of thinking and talking with other developers, I now believe that a reactive primitive could provide an overall better developer experience tha
I just finished rewriting an app from imperative code to completely reactive code. Here's the process I followed.
I converted a component from an imperative approach using NgRx/Component-Store to a completely reactive approach. I added local state to an event's payload to keep local and global state separate. I also created a declarative toast wrapper component.
I converted a component from an imperative approach using NgRx/Component-Store to a completely reactive approach. I decide to create a wrapper component for reactive router navigations. I also decide to define some reactive utilities for NgRx/Component-Store to handle state updates reactively.
I implemented the Angular Ionic Movies app with StateAdapt and the state management code decreased by 62% from what it was using NGXS.
YouTube video for this article I implemented the Account Menu in Angular Movies with StateAdapt and...
I implemented the Angular Movies app shell with StateAdapt and the code decreased by 50%.
I implemented Todo MVC with StateAdapt and the code decreased by 31%.
Easily guaranteeing consistency with NgRx/Store and NGX
Easily guaranteeing consistency with NgRx/Component-Store, Akita, Elf, RxAngular and RxJS.
Easily guaranteeing consistency with NgRx, NGXS, Akita, Elf, RxJS and StateAdapt.
Easily guaranteeing consistency by wrapping imperative APIs in Angular.
Easily guaranteeing consistency with multi-store selectors.
Easily guaranteeing consistency with multi-store DOM events.
Easily guaranteeing consistency with asynchronous sources.
Easily guaranteeing consistency with reusable state patterns.
Easily guaranteeing consistency with complex changes and derived state.
Easily guaranteeing consistency with simple derived state.
Guaranteed consistency doesn't have to be hard.
Why and how to manage state for Angular Reactive Forms
Why I didn't just use NgRx, NGXS or Subjects in a Service
Angular Reactive Forms makes your code look a lot like jQuery code, even if they're different under the hood.