You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per RFC 5789. Mechanically, the data being sent up should be similar to what's being done for a PUT, even if the semantics are all not the same (PUT's are usually for whole object replacements, PATCH's are usually for partial updates to existing objects).
The documentation can probably be folded into the header PUT Requests under a more inclusive name. Testing is a bit more involved, but can be done after the main implementation and documentation, which should be easy.
The text was updated successfully, but these errors were encountered:
As per RFC 5789. Mechanically, the data being sent up should be similar to what's being done for a PUT, even if the semantics are all not the same (PUT's are usually for whole object replacements, PATCH's are usually for partial updates to existing objects).
The curl option to set is this:
The documentation can probably be folded into the header
PUT Requests
under a more inclusive name. Testing is a bit more involved, but can be done after the main implementation and documentation, which should be easy.The text was updated successfully, but these errors were encountered: