Has anyone here had experience architecting their ...
# rx
d
Has anyone here had experience architecting their App such that each field of their entities is a BehaviorSubject? I get how using Subjects as stages of processing is tantamount to re-inventing imperative through Rx APIs and thereby 'misses the point'. But for data in it's 'rest state' this approach is actually seeming quite attractive... thoughts?