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
PATCH is used to update a resource and missing fields of the request are treated as "non-changed" fields - we should then provide a mechanism to delete (or null out) a field. I would suggest that passing in "null" to mean null out a field - and I would make a "null" value for a field the same as deleting the field. I'm not sure there's value in an optional field being there with a value of "null".
The text was updated successfully, but these errors were encountered:
Do we have usecases for nulling out fields? I can see value only when we talk about labels/ parameters (to remove a label or to remove a particular value of a label) but that should be already supported by the suggested approach to patch labels.
P.S. It's also debatable if the way suggested currently is the best to patch labels or managing labels as a subresource API would be better.
PATCH is used to update a resource and missing fields of the request are treated as "non-changed" fields - we should then provide a mechanism to delete (or null out) a field. I would suggest that passing in "null" to mean null out a field - and I would make a "null" value for a field the same as deleting the field. I'm not sure there's value in an optional field being there with a value of "null".
The text was updated successfully, but these errors were encountered: