You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating a record, the older version seems to persist in localStore. It happens like this:
In models index, go to edit form for an object.
Perform the update.
Be redirected to index, model hook fires but the enqueued update of step 2 didn't yet arrive to the server.
Fetch the index JSON object, with the not-yet-updated name.
Where's my update?
Now if I retrigger the index model hook, or reload, the update is of course there. Should localStore be the source of truth, and push changes always but not pull? Should online find not fire if there's enqueued operations? I'm not sure how to deal with this issue yet.
Thank you for your time.
The text was updated successfully, but these errors were encountered:
I like your approach, except that we shouldn't just check the queue. We should check if a particular item with same type and id is present. In that case, offlineStore takes precedence.
When updating a record, the older version seems to persist in localStore. It happens like this:
model
hook fires but the enqueued update of step 2 didn't yet arrive to the server.Now if I retrigger the index model hook, or reload, the update is of course there. Should localStore be the source of truth, and push changes always but not pull? Should online find not fire if there's enqueued operations? I'm not sure how to deal with this issue yet.
Thank you for your time.
The text was updated successfully, but these errors were encountered: