JSON Merge Patch Null Delete Marker Tool

Description

Parse patchJson.

JSON Patch describes operations at pointer locations, and operation context determines whether a location is usable. Array append tokens, root targets, and scalar equality have narrow semantics.

Parse patchJson.

When to use this tool

Use JSON Merge Patch Null Delete Marker when you need one explicit patch-context check.

How to use the tool and how it works

Enter patchJson. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read deleteMember, objectPatch. Inspect deleteMember, objectPatch before interpreting the associated values.

Parse patchJson. Mark deleteMember for literal null and objectPatch for a nonnull nonarray object.^[1]

A null member in an object merge patch requests deletion of that member. A nonobject patch instead replaces the target as a whole, so a top-level null and a null object member have different effects.^[2]

Input field	Meaning and units	Accepted input
patchJson	Patch Json	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
deleteMember	Whether the patch is literal null; deletion interpretation requires object-member context.	Required. Boolean.
objectPatch	Object Patch	Required. Boolean.

json

{
  "input": {
    "patchJson": "null"
  },
  "output": {
    "deleteMember": true,
    "objectPatch": false
  }
}

Limitations and assumptions

Null deletes a member only in an object merge-patch context; a root null patch replaces the document, and no patch is applied here.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Validate and apply the full patch transaction against the actual document using a conforming implementation.

References

Calculation and input contract: json/json-merge-patch-null-delete-marker — tool.io
JSON Merge Patch (RFC 7396) — RFC Editor / IETF

Similar or alternative tools

JSON: JSON Empty String Versus Missing Tag
Parse objectJson as an object and classify the literal key as missing, empty-string, null, or other using own-property presence before value checks.
JSON Patch Add Root Replacement Token
Require path empty or slash prefixed and set replacesDocument only for the empty root path.