feat: add revertKeyPath() and revertObject() methods to ParseObject #402
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Pull Request Checklist
Issue Description
After a developer begins mutating/updating a
ParseObject
that already has anobjectId
viamergeable
or some other method that allows the developer to save theParseObject
using the Parse Servers quirky patch. The only way to revert a specificKeyPath
back to its original value is by setting it based on a local stored version or remembering what that value was.Related issue: #n/a
Approach
Leverage the
originalData
property to allow developers to revert specificKeyPath
's or the wholeParseObject
.Example usage:
TODOs before merging