PATCH requires a diff media type about restcookbook HOT 7 OPEN

The problem is that PATCH does not need explicitly a diff media type. We could expand the recipe by adding a diff media type (like a diff output) and show the result (and point out the non-idempotency as a drawback)

A non-diff media-type, like the example given, should stay, but we could explain what the result would be, which in this case would that the firstname of the user will be changed (in a idempotent way).

from restcookbook.

The set of changes is represented in a format called a "patch
document" identified by a media type.

and

With PATCH, however, the enclosed entity contains a set
of instructions describing how a resource currently residing on the
origin server should be modified to produce a new version.

from restcookbook.

I will try and see if I can get this sorted a bit better.. to be honest, PATCH is defined pretty vaguely when it comes to their media types.

from restcookbook.

Yeah, I'm not 100% happy with the spec, but what are you gonna do?

from restcookbook.

amend it :) I think the restcookbook.com should be a way to give people at least some examples on how to implement this. I don't think it's perfect, but at least if we can give some examples, with the pros and cons, it would at least give people some insight without trying to invent everything by itself.

from restcookbook.

👍

from restcookbook.

PATCH and PUT doesn't have same content type! Please read "Please do not patch like an idiot".

from restcookbook.