Store
in ngrx case) via an Observable? Or about mutating the state (via an OBservable?! that's where I'm lost)?
store.select ()
is NOT subscribe in the sense of pub/sub?
the semantics should be:
I don't like the idea of wiring individual data elements between the view component and the state representation or the model.
@jdubray per your comment
any number of component can be notified of the changes (deltas) in the state representation
Is that a NAP responsibility (i.e., to "notify" listeners of changes)?
Or is that better handled elsewhere by the state (i.e., the state that makes the representation and calls render())?