Caching ?

[machard]

Hi,

I have a few questions about caching :

• With an infinite scroll where only the limit parameter is changing, it would be nice to only query the missing objects. Currently it is not so great : when the limit changes it renders a first time without the firsts elements then it rerenders with all elements. it causes flickering.
• It would be nice to add a mechanism to store/load the ObjectStore (allowing the developer to choose the method of his choice [Async Storage on react native, Locastorage/... on Web]) so that when returning to the app it displays the stored objects until it eventually gets updated. I guess Subscription would need changes too.
• I also want to store the mutations if they don't get a response when submitted to the server (if there is no available connection for example) and to replay them until it gets a response. Even if the tab (or the app) is closed/reopened. I believe changes would need to be implemented in the UpdateChannel (auto retry, and getting stored pending mutations on start) ?

This issue is more of a feedback afterall....

Currently i think i'll need to make my specific Store and Actions if i want to achieve the result i want.

Thank you

[ghost]

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.