Similar to the white/black list approach, attempts to validate paths with Reg Ex and glob patterns produced patterns that were much too complex.
The patterns would have to forbid unknown fields in one object and allow them in another.
If you don’t believe that these points are difficult to validate, I encourage you to validate an object as compared to its changes with any moderately complicated schema.
;)One my initial ideas was to iterate through every JSON Patch object and check the object against a set of rules.
Progress on the next set of Internet-Drafts can be tracked on Git Hub.
The draft-08 milestone will track the evolving scope of the draft You can apply constraints on an instance by adding validation keywords to the schema.
You can read more about JSON Schema at Internally Is Valid uses Json Validating Reader to perform the JSON Schema validation.
The JSON Schema project intends to shepherd the Core, Validation, and Hyper-Schema specifications to RFC status.I am not going to give a background on what a PATCH request is, so take a look at William Durand’s (unfortunately named) article, “Please.Don’t Patch Like An Idiot.”Database drivers generally do not natively support the JSON Patch spec (or not that I have seen).This means that the “op”, “path” and “value” fields in the Patch must all be checked against white and black lists.Coming up with an all-inclusive white/black list is possible, but would suffer from high maintenance costs when schema changes are made, and ensuring that 100% of the cases were covered could be a daunting task for any mildly complicated schema.