I have a SPA web app that uses ngrx. (I inherited that, maybe I wouldn't use ngrx if I implemented the thing myself). Can someone tell me if the concept of a "lazy data loading" is applicable to ngrx?
For example, there is a resource that is occasionally required by different components. Normally I would do a service that retrieves this resource from an external API. Internally, on the first request, the service is going to return an observable that will be filled in from a queried data + cached, so the future accesses will return an observable that already has the value.
Now, with NgRX I don't see a way to intervene at the access level, because there is no "logic" happening when the data is retrieved from the state.
Sure, I can query the resource upfront, but from the software design point of view, I don't want to care about "when" the query happens, I just want to know that it happens when it's needed.