updateCollection operations currently require
name to be specified in the update request. If the user doesn’t want to change the name — just some other attribute — they still have to pass the "name" (and make sure the value is the same so it doesn’t change). This is confusing and burdensome to the developer.
These operations would be clearer and easier to use if "name" were instead defined to be optional.
Why is it useful?
|Who would benefit from this IDEA?||As an application developer, I don't want to specify all fields when updating a collection or configuration|
How should it work?