rfc6902 | Complete implementation of RFC6902 in TypeScript | JSON Processing library

As answered by @chrylis, I would rather have to create a class with op, path, value, and from being the fields.

Let's abuse the fact that your classes are serializable to JSON! Here's a first attempt at a patch creator that doesn't care about your actual object, only about the JSON representation of that object.

Well I made it work by using the usual javascript reference from Starcounter-Jack/JSON-Patch. By loading it in the _layout.cshtml

You need 3 different states for email value here:

1. Filled value for update (e.g. test@mail.com)
2. null value if email should be removed
3. Missing value if email should not be touched.

So the problem actually is how to express these 3 states in string property of your model. You can't do this with just raw string property because null value and missing value will conflict as you correctly described. Solution is to use some flag that indicates whether the value was provided in the request. You could either have this flag as another property in your model or create a simple wrapper over string, very similar to Nullable class. I suggest creation of simple generic OptionalValue class:

The intent of the RFC6902 is not quite compatible with the DDD approach. This RFC is used to define a protocol used to mutate an object in a CRUD style, as opposed to DDD style. DDD focuses on the business behaviors using the ubiquitous language, whereas CRUD focuses on the data.

If you really want, you could use the RFC6902 for the command side (aka the write side) of the application. Every PATCH request would map to one or more commands that will be send to a single aggregate identified by the URL of the Request. Also, only the add operation makes sense, as in add and process a new command. For some commands, the remove operation could make sense but this is even more weird.

So, a request could look like this: