* Review and extend the documentation, and check it in CI A review of all documentation pages found factual errors, dead links, missing cross-references, and gaps in examples. This fixes them and adds checks so the same problems are caught automatically. Fixes: - wrong signatures and version histories (operator!= C++20 member, binary() subtype type, get<PointerType>(), JSON_NO_THREAD_LOCAL, ...) - stale descriptions (number parsing since #5283, UBJSON table, SAX example that no longer compiled, tsl::ordered_map advice) - dead internal and external links; repology.org badges (the domain is suspended) replaced by badges that query the registries directly - deprecation notes link the migration guide; the guide itself fixed Additions: - "See also" sections, cross-references, 25 runnable examples, 12 Mermaid diagrams, new API pages for json_pointer::operator<=> and byte_container_with_subtype::operator==/!= - landing page, guides for untrusted input and performance - "unreleased" badge after versions newer than the latest release Checks: - strict documentation build (broken links/anchors fail it); CI and the publish workflow fetch the full history the build needs - weekly external link check, Mermaid syntax check in CI - check_structure.py: example titles, heading levels, alt texts, header links, docset index coverage; its unused-example check works again - all examples produce the same output on every platform Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Keep the customer links that could not be fixed A dead link on the customers page is still the evidence of where the use of the library was documented. Keep the original URLs of the entries without a working replacement (Marne, Cisco Webex Desk Camera, Philips Hue, CyberArk) and exclude exactly these URLs from the link check. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct the duplicate-key recipe's claim about SAX positions The SAX interface's key() receives no position either; only parse_error() does. Also note that the recipe does not report the path to the repeated key (see discussion #5085). Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Say the library is available as a single header and mention json_fwd.hpp Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct documentation errors found while hunting for bugs - patch/patch_inplace: list the JSON pointer errors parse_error.106-109 and out_of_range.402/404, and quote the actual parse_error.105 message. - unflatten: list parse_error.106/107/108 and out_of_range.404. - to_bson: list out_of_range.415 (binary subtype above 255) and note that 412 and 415 are new in 3.13.0. - to_string: state that string_t must be convertible to std::string, also in the StringType requirements table. - JSON Lines: a `while (input >> j)` loop also throws after the last value for concatenated JSON values; show a loop that works for both. - BON8: a string gets 0xFF only if nothing follows it in the message; a string at the end of an array or object is ended by 0xFE. - custom_string_type.hpp: add operator+=(char), which the "Always required" list asks for (json_pointer::to_string, flatten, unflatten, and diff did not compile), and an ADL int_to_string for diff and items. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Cache the release headers with functools.lru_cache Codacy (Pylint) flagged the mutable default argument that header() used as its cache. functools.lru_cache keeps the same memoization without it. The script's output is unchanged. Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>
4.9 KiB
nlohmann::basic_json::update
// (1)
void update(const_reference j, bool merge_objects = false);
// (2)
void update(const_iterator first, const_iterator last, bool merge_objects = false);
- Inserts all values from JSON object
j. - Inserts all values from range
[first, last)
When merge_objects is #!c false (default), existing keys are overwritten. When merge_objects is #!c true,
recursively merges objects with common keys.
If the JSON value is #!json null, it is implicitly converted to an empty object before the values are inserted.
The function is motivated by Python's dict.update function.
Iterator invalidation
For ordered_json, adding a value to an object can yield a reallocation, in which case all
iterators (including the end() iterator) and all references to the elements are invalidated.
Parameters
j(in)- JSON object to read values from
merge_objects(in)- when
#!c true, keys that exist in both objects and whose value in the source is itself an object are merged recursively; all other values are overwritten as usual (default:#!c false) first(in)- the beginning of the range of elements to insert
last(in)- the end of the range of elements to insert
Exception safety
Basic guarantee: if an exception is thrown during the operation, the JSON value may be partially modified.
Exceptions
- The function can throw the following exceptions:
- Throws
type_error.312if called on JSON values other than objects; example:"cannot use update() with string"
- Throws
- The function can throw the following exceptions:
- Throws
type_error.312if called on JSON values other than objects; example:"cannot use update() with string" - Throws
invalid_iterator.210iffirstandlastdo not belong to the same JSON value; example:"iterators do not fit"
- Throws
Complexity
- O(N*log(size() + N)), where N is the number of elements to insert.
- O(N*log(size() + N)), where N is the number of elements to insert.
Notes
The argument j (or, for overload (2), the range [first, last)) may be #!cpp *this itself or refer to a value
contained in #!cpp *this (for example, a subobject returned by #!cpp (*this)[key]); it is read as it was when
update() was called, before any modification of #!cpp *this.
Examples
??? example "Example: (1) update with another object"
The example shows how `update()` is used.
```cpp
--8<-- "examples/update.cpp"
```
Output:
```json
--8<-- "examples/update.output"
```
??? example "Example: (2) update with an iterator range"
The example shows how `update()` is used.
```cpp
--8<-- "examples/update__range.cpp"
```
Output:
```json
--8<-- "examples/update__range.output"
```
??? example "Example: (1) merge user settings into default settings"
One common use case for this function is the handling of user settings. Assume your application can be configured in
some aspects:
```json
{
"color": "red",
"active": true,
"name": {"de": "Maus", "en": "mouse"}
}
```
The user may override the default settings selectively:
```json
{
"color": "blue",
"name": {"es": "ratón"},
}
```
Then `update` manages the merging of default settings and user settings:
```cpp
auto user_settings = json::parse("config.json");
auto effective_settings = get_default_settings();
effective_settings.update(user_settings);
```
Now `effective_settings` contains the default settings, but those keys set by the user are overwritten:
```json
{
"color": "blue",
"active": true,
"name": {"es": "ratón"}
}
```
Note existing keys were just overwritten. To merge objects, `merge_objects` setting should be set to `#!c true`:
```cpp
auto user_settings = json::parse("config.json");
auto effective_settings = get_default_settings();
effective_settings.update(user_settings, true);
```
```json
{
"color": "blue",
"active": true,
"name": {"de": "Maus", "en": "mouse", "es": "ratón"}
}
```
See also
- insert add values to an array/object
- merge_patch applies a JSON Merge Patch
- Modifying values - the article on modifying values
Version history
- Added in version 3.0.0.
- Added
merge_objectsparameter in 3.10.5. - Fixed use of freed or relocated memory when the argument is
#!cpp *thisor refers to a value contained in#!cpp *this, in version 3.13.0.