For consideration pre-1.0:
Commit 01ce345 changes all references of PUT to PATCH. 👍 for RFC 5789 compliance, but it opens a couple of questions:
- There is no longer explicit support for full-replacement updates via the
PUT method. Devs familiar with PUT but not PATCH may find it strange that it isn't mentioned at all.
- Suggestion: specify that servers MAY support the
PUT method, but it MUST only be used for full-replacement updates.
- RFC 5789 says "If the Request-URI does not point to an existing resource, the server MAY create a new resource, depending on the patch document type (whether it can logically modify a null resource) and permissions, etc.". The json-api spec does not currently offer guidance on this.
- Suggestion: explicitly say whether or not this is allowable under json-api. If there is no strong guidance deemed necessary, then a best-practice suggestion could be added to Recommendations.
For consideration pre-1.0:
Commit 01ce345 changes all references of
PUTtoPATCH. 👍 for RFC 5789 compliance, but it opens a couple of questions:PUTmethod. Devs familiar withPUTbut notPATCHmay find it strange that it isn't mentioned at all.PUTmethod, but it MUST only be used for full-replacement updates.