* docs: new design for the documentation site Apply the brand to the Material for MkDocs site: Inter and JetBrains Mono served by the site (upright and real italic), brand colours, blue header band with the syntax pattern, wordmark in the header, new home page (hero, cards, animated feature tour), 404 page, polish for tabs, search, footer, focus rings, tables and code blocks, and theme features (code copy, previous/next footer, TOC follow, search suggestions). Draw the number railroad diagram, the parser callback events and the iterator illustrations as inline SVGs that follow the light and dark scheme. The generator scripts are in docs/mkdocs/scripts/figures; the feature slideshow (json-light.svg, json-dark.svg, replacing json.gif on the home page) is built by docs/mkdocs/scripts/slideshow. Decision nodes in five flowcharts become hexagons, which need far less room. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: add figures, table captions and a macro chooser - Figures with numbered captions: SAX stepper, json_view layout and edit stepper, exception map, JSON pointer and patch walkers, QA pipeline, scaling and binary size charts, roadmap lanes, release timeline, integration decision tree and namespace builder - Table captions (nj-table-caption) on 9 pages - Compile times: modules and PCH charts, filesystem section, re-measured Figure 1, links between features/modules.md and compile_times.md - Interactive macro chooser for features/arbitrary_types.md - Link check: exclude URLs that answer the plugin with 400/401/419 or are dead (customers.md) Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: macro chooser generates adl_serializer for non-default-constructible types Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: cross-link concept pages and API pages in See also sections Add See also links in both directions between the concept pages (features, home, integration) and the API pages, write API links in code font, give every entry a comment after a dash, and show the callback event figure on the parser callbacks page. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: address review comments on the new design - Home: add a "Latest release" button - Sponsors: update the list and group it by tier - Features: list all feature pages on the index page - Releases: add highlights per release, link the 4.0 roadmap, add the first commit to the timeline - Exceptions: prefix all example messages with the exception name - API: no code font for format names in the See also links of the to_/from_ pages - Merge Patch: show the document before, the patch, and the result - Replace "--" with typographic dashes, mark external links with an icon, center Mermaid diagrams Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>
4.3 KiB
nlohmann::basic_json::merge_patch
void merge_patch(const basic_json& apply_patch);
The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content. This function applies a merge patch to the current JSON value.
The function implements the following algorithm from Section 2 of RFC 7396 (JSON Merge Patch):
define MergePatch(Target, Patch):
if Patch is an Object:
if Target is not an Object:
Target = {} // Ignore the contents and set it to an empty Object
for each Name/Value pair in Patch:
if Value is null:
if Name exists in Target:
remove the Name/Value pair from Target
else:
Target[Name] = MergePatch(Target[Name], Value)
return Target
else:
return Patch
Thereby, Target is the current object; that is, the patch is applied to the current value.
Parameters
apply_patch(in)- the patch to apply
Exception safety
Basic guarantee: if an exception is thrown during the operation, the JSON value may be partially modified.
Complexity
Linear in the total number of values (including nested ones) in apply_patch, times the cost of a key-based object
operation (looking up, adding, or erasing a member): logarithmic for json, and linear for
ordered_json (see ordered_map complexity). For
ordered_json, patching an object that has n members with a patch that has m members therefore takes O(n·m). The
cost also includes one copy of apply_patch (see the notes below).
Notes
apply_patchmay be#!cpp *thisitself or refer to a value contained in#!cpp *this(for example, a subobject returned by#!cpp (*this)[key]); it is read as it was whenmerge_patch()was called, before any modification of#!cpp *this. To make this possible, the function copiesapply_patchbefore it modifies#!cpp *this, so the cost includes one copy of the patch.- A merge patch uses
#!json nullto remove a member, so it cannot set a member to#!json null: applying#!json {"a":null}to#!json {"a":1}gives#!json {}. - Arrays are not merged: an array in the patch replaces the target value as a whole, and a
#!json nullinside an array is kept as an element.#!json nullmembers of the target that the patch does not mention are preserved. - A
#!json nullin the patch only removes a member; it does not prevent the creation of the enclosing objects. Applying#!json {"a":{"b":null}}to#!json {}gives#!json {"a":{}}(see example 15 in Appendix A of the RFC). - If
apply_patchis not an object, it replaces the target as a whole. In particular, a#!json nullpatch turns the target into#!json null. Ifapply_patchis an object and the target is not, the target is first replaced by an empty object, so applying#!json {}to#!json 1gives#!json {}. - A merge patch cannot express every change; for example, it cannot reorder array elements or remove a specific array
element. Use JSON Patch (RFC 6902) for that.
merge_diffhas a matching limitation, see its notes. - A discarded value is treated like any other non-object value: a discarded
apply_patchturns the target into a discarded value, and an object patch replaces a discarded target by an object as described above.
Examples
??? example
The following code shows how a JSON Merge Patch is applied to a JSON document.
```cpp
--8<-- "examples/merge_patch.cpp"
```
Output:
```json
--8<-- "examples/merge_patch.output"
```
See also
- RFC 7396 (JSON Merge Patch) - specification of JSON Merge Patch
patch- apply a JSON patchmerge_diff- creates a diff as a JSON Merge Patch- JSON Merge Patch - the article on JSON Merge Patch
Version history
- Added in version 3.1.0.
- Fixed use of freed or relocated memory when
apply_patchis#!cpp *thisor refers to a value contained in#!cpp *this, in version 3.13.0.