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
{{ message }}
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.
Local attributes for models that are not yet synced can be lost after save(attrs, {patch: true})
A model will have a temporary id when it is recently created and has not yet been successfully synced.
When an un-synced model is updated with patch: true and the server responds with a partial or empty set of attributes, attributes not in the server response will be missing in the local copy. This happens because the unsynced version is discarded, and a new model is created locally. See backbone.dualstorage.coffee:271.
It instead should update the existing local model's attributes with the server response, just as it does for a synced model. #51 may change the way attributes are updated, so it may be best to wait to fix this until that is resolved.
The text was updated successfully, but these errors were encountered:
Local attributes for models that are not yet synced can be lost after
save(attrs, {patch: true})
A model will have a temporary id when it is recently created and has not yet been successfully synced.
When an un-synced model is updated with
patch: true
and the server responds with a partial or empty set of attributes, attributes not in the server response will be missing in the local copy. This happens because the unsynced version is discarded, and a new model is created locally. See backbone.dualstorage.coffee:271.It instead should update the existing local model's attributes with the server response, just as it does for a synced model.
#51 may change the way attributes are updated, so it may be best to wait to fix this until that is resolved.
The text was updated successfully, but these errors were encountered: