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
Notice that the displayFormat does not change until the final PUT request. Sometimes this final PUT with the changed value is never fired off, in which case the property is failed to update locally and in persistence.
So it looks like there are a couple of things happening here.
First, EditPropertiesAction was refactored to use mutate against every property, regardless of whether or not it was changed. This means that changing one object property while using CouchDB ends up firing a PUT request to Couch for every editable property on the object.
Secondly, the Object tree was modified to listen for domainObject name changes in order to automatically alphabetize the tree. Since editing the properties will emit a change event for the 'name' regardless of whether or not it actually changed, this is firing before the CouchDB transaction completes and recreating the object tree with the outdated revision.
This has implications for editing properties on any domainObject while using CouchDB. We need a way to wait for the CouchDB transaction to complete before alphabetizing the tree again.
When running CouchDB locally, I tried the following:
I am seeing multiple requests to CouchDB after hitting 'Save':
Notice that the
displayFormat
does not change until the final PUT request. Sometimes this final PUT with the changed value is never fired off, in which case the property is failed to update locally and in persistence.Originally posted by @ozyx in #5398 (comment)
The text was updated successfully, but these errors were encountered: