bigskysoftware
PUT vs. PATCH clarification
@codetalcott Is there any disagreement over whether this is a good change?
Deploy Preview for hypermedia-systems ready!
| Name | Link |
|---|---|
| Latest commit | 8ea4d809743779086d19e38000a50e21f9385438 |
| Latest deploy log | https://app.netlify.com/sites/hypermedia-systems/deploys/659ea460f9a2b600083e9bc5 |
| Deploy Preview | https://deploy-preview-124--hypermedia-systems.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @mvolkmann do you think that langauge is defensible given the discussion here:
https://stackoverflow.com/questions/28459418/use-of-put-vs-patch-methods-in-rest-api-real-life-scenarios
Maybe we should use the RFC language, or at least reference it?
Sure, using words from that post is fine with me. So instead of my suggestion to add the word "all" for PUT, we would add "a modified version" and instead of my suggestion to add the words "some of" for PATCH we would add "a set of changes".
I have integrated a slightly modified version of this change into our new repository. We will make that repo public soon, thank you!