Simple and basic RxJS provides everything you need with much less code (StackBlitz Example).
It provides a Single Source of Truth for the application's data and states.
You do not have Single Source of Truth, because it does not mean that you have one class to handle the data, it means you have one immutable object with all the actual data in it.
It centralizes the process of triggering actions.
With basic RxJS you do not even need actions, you just call service methods.
It allows for a location for "global" functionality.
So can every providedIn: 'root' service
It provides a central location for all components and services to see data and state changes.
Putting everything in one class is not a central location and it will quickly become hard to use.
FYI … pretty sure I explained it’s an exercise. Think a of this as an academic exercise in what “could” be done. For me, it provided a better understanding of all the tooling involved and pulled together some ideas in a way that made some concepts clearer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As for the pattern, it's just overengineering.
Simple and basic RxJS provides everything you need with much less code (StackBlitz Example).
You do not have Single Source of Truth, because it does not mean that you have one class to handle the data, it means you have one immutable object with all the actual data in it.
With basic RxJS you do not even need actions, you just call service methods.
So can every
providedIn: 'root'servicePutting everything in one class is not a central location and it will quickly become hard to use.
I’m glad you enjoyed the article!
FYI … pretty sure I explained it’s an exercise. Think a of this as an academic exercise in what “could” be done. For me, it provided a better understanding of all the tooling involved and pulled together some ideas in a way that made some concepts clearer.