mirror of
https://github.com/nlohmann/json.git
synced 2026-10-03 05:00:30 +00:00
* 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>
162 lines
4.4 KiB
Markdown
162 lines
4.4 KiB
Markdown
# Iterators
|
|
|
|
## Overview
|
|
|
|
A `basic_json` value is a container and allows access via iterators. Depending on the value type, `basic_json` stores zero or more values.
|
|
|
|
As for other containers, [`begin()`](../api/basic_json/begin.md) returns an iterator to the first value and
|
|
[`end()`](../api/basic_json/end.md) returns an iterator to the value following the last value. The latter iterator is a
|
|
placeholder and cannot be dereferenced. In case of null values, empty arrays, or empty objects, `begin()` will return
|
|
`end()`.
|
|
|
|

|
|
|
|
### Iteration order for objects
|
|
|
|
When iterating over objects, values are ordered with respect to the `object_comparator_t` type which defaults to `std::less`. See the [types documentation](types/index.md#key-order) for more information.
|
|
|
|
??? example "Example: iteration order of object values"
|
|
|
|
```cpp
|
|
// create JSON object {"one": 1, "two": 2, "three": 3}
|
|
json j;
|
|
j["one"] = 1;
|
|
j["two"] = 2;
|
|
j["three"] = 3;
|
|
|
|
for (auto it = j.begin(); it != j.end(); ++it)
|
|
{
|
|
std::cout << *it << std::endl;
|
|
}
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
1
|
|
3
|
|
2
|
|
```
|
|
|
|
The reason for the order is the lexicographic ordering of the object keys "one", "three", "two".
|
|
|
|
### Access object keys during iteration
|
|
|
|
The JSON iterators have two member functions, `key()` and `value()` to access the object key and stored value, respectively. When calling `key()` on a non-object iterator, an [invalid_iterator.207](../home/exceptions.md#jsonexceptioninvalid_iterator207) exception is thrown.
|
|
|
|
??? example "Example: access object keys with `key()` and `value()`"
|
|
|
|
```cpp
|
|
// create JSON object {"one": 1, "two": 2, "three": 3}
|
|
json j;
|
|
j["one"] = 1;
|
|
j["two"] = 2;
|
|
j["three"] = 3;
|
|
|
|
for (auto it = j.begin(); it != j.end(); ++it)
|
|
{
|
|
std::cout << it.key() << " : " << it.value() << std::endl;
|
|
}
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
one : 1
|
|
three : 3
|
|
two : 2
|
|
```
|
|
|
|
### Range-based for loops
|
|
|
|
C++11 allows using range-based for loops to iterate over a container.
|
|
|
|
```cpp
|
|
for (auto it : j_object)
|
|
{
|
|
// "it" is of type json::reference and has no key() member
|
|
std::cout << "value: " << it << '\n';
|
|
}
|
|
```
|
|
|
|
For this reason, the [`items()`](../api/basic_json/items.md) function allows accessing `iterator::key()` and
|
|
`iterator::value()` during range-based for loops. In these loops, a reference to the JSON values is returned, so there
|
|
is no access to the underlying iterator.
|
|
|
|
```cpp
|
|
for (auto& el : j_object.items())
|
|
{
|
|
std::cout << "key: " << el.key() << ", value:" << el.value() << '\n';
|
|
}
|
|
```
|
|
|
|
The items() function also allows using structured bindings (C++17):
|
|
|
|
```cpp
|
|
for (auto& [key, val] : j_object.items())
|
|
{
|
|
std::cout << "key: " << key << ", value:" << val << '\n';
|
|
}
|
|
```
|
|
|
|
!!! note
|
|
|
|
When iterating over an array, `key()` will return the index of the element as string. For primitive types (e.g., numbers), `key()` returns an empty string.
|
|
|
|
!!! warning
|
|
|
|
Using `items()` on temporary objects is dangerous. Make sure the object's lifetime exceeds the iteration. See [#2040](https://github.com/nlohmann/json/issues/2040) for more information.
|
|
|
|
### Reverse iteration order
|
|
|
|
[`rbegin()`](../api/basic_json/rbegin.md) and [`rend()`](../api/basic_json/rend.md) return iterators in the reverse
|
|
sequence.
|
|
|
|

|
|
|
|
??? example "Example: reverse iteration with `rbegin()` and `rend()`"
|
|
|
|
```cpp
|
|
json j = {1, 2, 3, 4};
|
|
|
|
for (auto it = j.rbegin(); it != j.rend(); ++it)
|
|
{
|
|
std::cout << *it << std::endl;
|
|
}
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
4
|
|
3
|
|
2
|
|
1
|
|
```
|
|
|
|
### Iterating strings and binary values
|
|
|
|
Note that "value" means a JSON value in this setting, not values stored in the underlying containers. That is, `*begin()` returns the complete string or binary array and is also safe if the underlying string or binary array is empty.
|
|
|
|
??? example "Example: iterate over a string value"
|
|
|
|
```cpp
|
|
json j = "Hello, world";
|
|
for (auto it = j.begin(); it != j.end(); ++it)
|
|
{
|
|
std::cout << *it << std::endl;
|
|
}
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
"Hello, world"
|
|
```
|
|
|
|
## Iterator invalidation
|
|
|
|
| Operations | invalidated iterators |
|
|
|------------|-----------------------|
|
|
| `clear` | all |
|