Make Backbone PROPPATCH work with options.wait mode#28767
Conversation
f810792 to
2b6fa66
Compare
There was a problem hiding this comment.
It makes me wonder if this has ever worked... Does this link with the davSync method below? If so, any reason to move the JSON.stringify up here?
There was a problem hiding this comment.
We have some custom calls (ex: comments app) where it does a plain POST with JSON on the collection. Later on we decided that we didn't want POST any more with Webdav so we're now using other methods. The reason I moved this down is because the stringification is only needed for this one code path.
|
Need to check the failing tests. |
|
At the moment: |
2b6fa66 to
29554a4
Compare
|
rebased. now that the other fix is in I expect all will pass |
In options.wait mode, no model.changes are available as they haven't been set yet. So in this mode we simply get all properties and send these with PROPPATCH.
29554a4 to
f819148
Compare
|
stable10: #28791 |
|
Regression: #28826 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
In options.wait mode, no model.changes are available as they haven't
been set yet. So in this mode we simply get all properties and send
these with PROPPATCH.
Related Issue
Fixes owncloud/customgroups#87
Motivation and Context
Better compatibility with backbone options.
How Has This Been Tested?
Manual testing with customgroups ticket and JS unit test.
Screenshots (if appropriate):
Types of changes
Checklist: