To me, the need for this is obvious; it helps to shrink the amount of data that is being sent back and forth, when the data itself being worked with is small too.
For scaling and heavy load optimization purposes, this could prove a crucial feature. Thus it should be supported by the API.
When interacting with a single property of an existing element, such as
the price for a productthe name of an userit makes sense to only send that specific piece of data, instead of sending the whole object containing the updated property.
At least, this is my interpretation of what
PATCHmethods are meant for.And here's a better description of what more precisely it is supposed to be.
To me, the need for this is obvious; it helps to shrink the amount of data that is being sent back and forth, when the data itself being worked with is small too.
For scaling and heavy load optimization purposes, this could prove a crucial feature. Thus it should be supported by the API.