Closed mortenmo closed 6 months ago
I will reformat the title to use the proper commit message syntax.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 100.00%. Comparing base (
72bc9ac
) to head (da3121c
). Report is 15 commits behind head on alpha.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@mtrezza @mortenmo A PR for this has already been opened. Try copying the test over from that PR. I'll review.
I really need to check existing PRs better :) . The fixes looks basically identical, so feel free to commit that one and I can close this one. I added the #1450 test case here just to be sure and it does also pass.
Hey. I made some changes to #1451 . The patch also handles doubly-nested objects now, it used to be still broken in that case. I also modified the regression test to also include this scenario.
Is this PR made obsolete by https://github.com/parse-community/Parse-SDK-JS/pull/1451? If not, which one should be merged first, in case order matters?
I believe so. I copied the new regression test in this branch over to my branch, and it does pass there also.
I would suggest #1451 to be merged in favor of this one, as that one implements a more robust deep cloning logic after today's changes, evidenced by the regression test here passing there, but not vica versa.
Pull Request
Issue
Closes: https://github.com/parse-community/Parse-SDK-JS/issues/2115 Closes: https://github.com/parse-community/Parse-SDK-JS/pull/1451
Approach
When local state has multiple set/unset ops on the same base property, use the result of the previous instead of always going back to the server version for every Op to allow them to chain.
The test included fails until the fix is in place.
Tasks