Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for #1840, Strip operations from results, forwards delete operations to SDKs #1946

Merged
merged 8 commits into from
Jul 15, 2016

Conversation

flovilmart
Copy link
Contributor

@flovilmart flovilmart commented May 29, 2016

After a DB operation that was mutated by a beforeSave we'd loop through the new keys in order to set the DB computed values or the original value.

We strip all operations from the results, as the clients can't interpret it.

For compatible SDK's we reinject the delete ops so the client can safely remove the associated key without fetching again.

Fixes #1840
Closes #1940
Fixes #1606

@codecov-io
Copy link

codecov-io commented May 29, 2016

Current coverage is 91.87%

No coverage report found for master at 4e9e817.

Powered by Codecov. Last updated by 4e9e817...6bd72bc

@flovilmart flovilmart changed the title Proposed fix for #1840 WIP: Proposed fix for #1840 May 29, 2016
@flovilmart
Copy link
Contributor Author

After further investigation, the Parse.com behaves the same way which is troubling...

@facebook-github-bot
Copy link

@flovilmart updated the pull request.

@flovilmart
Copy link
Contributor Author

Will be fixed by: parse-community/Parse-SDK-JS#289

@flovilmart
Copy link
Contributor Author

This won't work as is, as the Client SDK's don't handle (at all the Delete operations when coming back from the server...)

@flovilmart
Copy link
Contributor Author

Waiting for the JS-SDK that implement the change to be released.

@TylerBrock
Copy link
Contributor

We might be able to test this functionality with 1.9.0-rc1 now.

@flovilmart
Copy link
Contributor Author

I don't see it yet

@ghost
Copy link

ghost commented Jul 8, 2016

@flovilmart updated the pull request.

@ghost
Copy link

ghost commented Jul 8, 2016

@flovilmart updated the pull request.

@flovilmart flovilmart changed the title WIP: Proposed fix for #1840 Fix for #1840, forwards delete operations to SDKs Jul 8, 2016
@ghost
Copy link

ghost commented Jul 12, 2016

@flovilmart updated the pull request.

@drew-gross
Copy link
Contributor

Something in here is causing the tests to consistently fail in postgres. Not sure what, excluding progres is probably fine though.

@ghost
Copy link

ghost commented Jul 12, 2016

@flovilmart updated the pull request.

@flovilmart
Copy link
Contributor Author

@drew-gross we may want to add a check on the client SDK version for the support of that feature no?

@ghost
Copy link

ghost commented Jul 12, 2016

@flovilmart updated the pull request.

2 similar comments
@ghost
Copy link

ghost commented Jul 12, 2016

@flovilmart updated the pull request.

@ghost
Copy link

ghost commented Jul 12, 2016

@flovilmart updated the pull request.

@flovilmart flovilmart changed the title Fix for #1840, forwards delete operations to SDKs WIP: Fix for #1840, forwards delete operations to SDKs Jul 12, 2016
@flovilmart flovilmart modified the milestone: 2.2.17 Jul 12, 2016
@flovilmart flovilmart changed the title WIP: Fix for #1840, forwards delete operations to SDKs Fix for #1840, forwards delete operations to SDKs Jul 12, 2016
@flovilmart flovilmart changed the title Fix for #1840, forwards delete operations to SDKs Fix for #1840, Strip operations from results, forwards delete operations to SDKs Jul 13, 2016
@flovilmart flovilmart merged commit 069275d into master Jul 15, 2016
@flovilmart flovilmart deleted the fix-1840 branch July 15, 2016 13:24
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Mar 15, 2017
… delete operations to SDKs (parse-community#1946)

* Adding a test demonstrating issue parse-community#1840.

* Fixes parse-community#1840

* Adds failing test with other use case

- That test fails on parse.com as well

* Bumps parse to 1.9.0

* exclude pg db

* Exclude pg on other test

* Adds clientSDK compatibility check for forward deletion

- Mark js1.9.0 as compatible

* Strips all operations from result

- fix for parse-community#1606
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Mar 16, 2017
… delete operations to SDKs (parse-community#1946)

* Adding a test demonstrating issue parse-community#1840.

* Fixes parse-community#1840

* Adds failing test with other use case

- That test fails on parse.com as well

* Bumps parse to 1.9.0

* exclude pg db

* Exclude pg on other test

* Adds clientSDK compatibility check for forward deletion

- Mark js1.9.0 as compatible

* Strips all operations from result

- fix for parse-community#1606
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants