Daniel
Daniel
Right, you're much more familiar with Swift and POP than I am, so I can't confidently argue either way. It just seems strange to me that updating an object with...
Right, so the consideration here to be aware of, is that if you use Parse Swift, calling `.save` on an existing object, will _always_ send all keys to be updated,...
The main concern for the server PR is to make sure cloud functions that use `.dirty` and `dirtyKeys` can be use as expected with ParseSwift
That sounds like a good solution to me!
My understanding is that if a developer uses `emptyObject`, they still need to compare the updated fields to the fields on fetch. E.g, 1. object is fetched 2. text fields...
> The Swift SDK doesn't work like this. If a developer is "enumerating through keys" in the first example you showed, you set the required fields to emptyObject, and then...
> If a developer wants/needs dirty Purely from an optimisation perspective, I don’t understand where a developer wouldn’t need dirty. For newer devs, sending the whole object all the time...
I’m sure I’ve said this before, but if a key is set to increment, and a developer uses `operations` to increment it, if they save without `emptyObject` it will override...
You're awesome @cbaker6 👏