The e-book example makes the methods easy to follow, especially PUT needing the full book data while PATCH only sends the fields that change. That difference is what usually trips people up when an API update wipes a field by accident. Having the status codes right after the methods works well as a quick reference.
StackShortlist
Proof Over Promises.
The e-book example makes the methods easy to follow, especially PUT needing the full book data while PATCH only sends the fields that change. That difference is what usually trips people up when an API update wipes a field by accident. Having the status codes right after the methods works well as a quick reference.