Is your feature request related to a problem? Please describe.
When saving an object in which properties there's a pointer to another object, the SDK launches a batch operation to save all modifications made to all nested objects, which is great but... when you don't have write access to any of those (for example when you're saving a Message object pointing to another user's profile) you need to make sure nested objects are not dirty or call rever() in order not to get the Object not found error.
Describe the solution you'd like
A parameter in the saving options, something like ParseObject.save(null, {cascadeSave: false}) would address this issue.
Describe alternatives you've considered
A workaround for now is to call Parse.Object.revert() on all objects to which you know this user does not have write permissions.
Is your feature request related to a problem? Please describe.
When saving an object in which properties there's a pointer to another object, the SDK launches a batch operation to save all modifications made to all nested objects, which is great but... when you don't have write access to any of those (for example when you're saving a Message object pointing to another user's profile) you need to make sure nested objects are not
dirtyor callrever()in order not to get theObject not founderror.Describe the solution you'd like
A parameter in the saving options, something like
ParseObject.save(null, {cascadeSave: false})would address this issue.Describe alternatives you've considered
A workaround for now is to call
Parse.Object.revert()on all objects to which you know this user does not have write permissions.