Very well put together, succinct article!
We don't use NgRX at my workplace, but we do have a couple of data source services.
They kind of just grew organically.
I see the benefits of following your rules of immutability, having a private behaviourSubject, and the getter and setter. Also the second readonly observable which pipes the behaviourSubject is very nice.
Is the term storeService a widely used suffix?
I currently use dataSourceService.
Very well put together, succinct article!
We don't use NgRX at my workplace, but we do have a couple of data source services.
They kind of just grew organically.
I see the benefits of following your rules of immutability, having a private
behaviourSubject, and the getter and setter. Also the second readonly observable which pipes thebehaviourSubjectis very nice.Is the term
storeServicea widely used suffix?I currently use
dataSourceService.Thanks!
nope it's up to you to name it, I usually name it something like TodosStore
I think I prefer the suffix store over dataSource.
Also the ngrx stuff talks about stores a lot. Seems to be a popular term.