* Split the json_view feature page into sub-pages
The single features/json_view.md page grew to ~600 lines covering eight
topics. Split it into features/json_view/ with an overview page and
pages for ownership and lifetime, differences from basic_json, reading
values, generic code, editing, and images.
The new differences page collects what was spread over several sections
("What is the same", "What is different", "Duplicate keys", and notes in
the conversion and serialization sections) under one summary table, and
adds the parts of the basic_json interface a view does not have. The
other pages now link to it instead of restating the rules.
Internal links across the documentation point to the new pages.
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
* Docs: fix stale comments and trim repeated text in json_view pages
- fig-jsonview.js/.css: point the header comments at the new pages
- reading.md: views' strings are valid as long as the document (and a
borrowed source text), as lifetime.md says
- reading.md, generic_code.md: link to differences.md instead of
restating the member-order and repeated-key rules
- differences.md: drop the third mention of ordering comparisons, name
rbegin()/rend() in the iterator row
- exceptions.md: link editable documents to editing.md
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
---------
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
5.0 KiB
Modifying values
Once a JSON value exists, its content can be changed: elements can be added, replaced, merged, and removed. This page gives an overview of the available operations. For read access, see element access.
Adding to arrays
New elements are appended to an array with push_back or constructed in place with
emplace_back. If the value is #!json null, it is converted to an array first, so
these functions can also be used to build an array from scratch.
json j; // null
j.push_back(1); // [1]
j.push_back(2); // [1,2]
j.emplace_back(3); // [1,2,3]
// operator+= is a shorthand for push_back
j += 4; // [1,2,3,4]
Adding to objects
The most common way to add or replace a member is operator[], which inserts the
key if it does not exist yet:
json j;
j["name"] = "Mary"; // {"name":"Mary"}
j["name"] = "John"; // {"name":"John"} (replaced)
emplace inserts a member only if the key is not already present, and reports whether
the insertion happened — useful for "add if absent" semantics.
Merging objects
To merge one object into another, update copies all members from another object
(similar to Python's dict.update). This is the idiomatic way to combine two objects. It has two modes:
- By default, the merge is shallow: existing keys are overwritten, even if both values are objects.
- With
merge_objects = #!cpp true, keys whose values are objects in both JSON values are merged recursively. Everything else is overwritten. In particular, arrays are replaced, not concatenated.
??? example
```cpp
--8<-- "examples/update.cpp"
```
Output:
```json
--8<-- "examples/update.output"
```
A common use of the recursive mode is combining defaults with user settings. Nested defaults that the user did not set are kept:
json defaults = {{"log", {{"level", "info"}, {"file", "app.log"}}}, {"retries", 3}};
json user_settings = {{"log", {{"level", "debug"}}}};
json config = defaults;
config.update(user_settings, true);
// {"log":{"file":"app.log","level":"debug"},"retries":3}
JSON Merge Patch (RFC 7396) also merges objects recursively,
but it is a different tool: a #!json null in the patch means "remove this key". It is meant for applying merge patch
documents (e.g., received via HTTP PATCH). To merge configuration-like objects, use #!cpp update(..., true). To apply
a sequence of well-defined edit operations, see JSON Patch.
Removing elements
Elements are removed with erase, which accepts an object key, an array index, or an
iterator. clear empties a value while keeping its type, and
operator[] combined with assignment can overwrite a value entirely.
json j = {{"a", 1}, {"b", 2}, {"c", 3}};
j.erase("b"); // {"a":1,"c":3}
json a = {1, 2, 3, 4};
a.erase(1); // [1,3,4] (erase by index)
Editing a document
The operations above work on a basic_json value. A JSON text that was parsed into a
document can also be changed in place, without building a basic_json tree for the
parts that are not touched: set replaces a value, adds or replaces an object
member, or replaces an array element (also through a JSON pointer),
push_back appends to an array,
insert inserts into an array (unlike basic_json::insert, it has no object
overload; members are added with set), and erase removes a member or an
element. These functions are available on the
editable document types, such as json_editable_document.
See also
push_back- /emplace_back- append to an arrayemplace- insert into an object if the key is absentupdate- merge objects (shallow, or recursive withmerge_objects)merge_patch- apply an RFC 7396 merge patcherase- /clear- remove elements- JSON Patch and Diff - and JSON Merge Patch - structured modifications
- Editing a document - change a parsed document in place
insert- insert elements at an iterator position or merge a rangeoperator+=- shorthand forpush_back- Element Access - read elements
- Iterators - iterate over elements