Putting it simply: do you ever use subscriptions to then put something back to the app-db?
@isak good tip, thanks a lot! However, this doesn’t use awesome caching things like subs [supposedly] do.
@lukas.rychtecky Thanks! Yeah, I’m hesitant also, but still – I don’t see negative scenarios yet. Apart from “shooting myself in the foot”. I agree that it’s an anti-pattern, for sure.
IMO you shouldn’t. Subs are “views” above the data. Only event handlers should change the app-db.
No, that is what interceptors are for. See the built-in on-changes
interceptor, for example.