Saved Query partial update

[masojus]

This change hasn't been properly tested and would need to be cleaned up before getting merged. The purpose is to show what would need to happen to enable partial updates to a Saved/Cached Query while trying to preserve remote changes (e.g. - changes made via the Project Explorer Web UI), and to discuss that a little bit.

• A README.rst change will probably need to happen either way, but if the follow-up change is accepted in a cleaned-up/tested manner, we can augment the readme to add a sample of the behavior we settle on.

[josephwegner]

Thoughts on changing update to do the partial updates, and add a new func update_full that does the whole thing. As it stands, I think leaving the default update as a full overwrite is still a big surface area for mistakes.

update should probably fall back to update_full if it is not passed the old definition.

Does that make any sense? Good idea? Bad idea?

[masojus]

I think if client devs are already using update() with a full definition, and not editing their queries elsewhere, then it's a good idea to keep supporting that flow, as you describe. I could think of better names if we could make the intent clearer and would accept input there, of course :)

[masojus]

I pushed the readme changes in a separate PR since those need to happen regardless. I'll work on cleaning this up, incorporating PR feedback and getting some tests in place.

[masojus]

I also need to update the README file to match this behavior.

[josephwegner]

This looks pretty good. Can we add some tests that check the different functionality of update and update_full? Or is that functionality untestable?

[masojus]

I can look into testing that giving a full definition behaves differently from a partial update in terms of absent properties.