mirror of
https://github.com/nlohmann/json.git
synced 2026-10-05 14:10:31 +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>
133 lines
4.6 KiB
Markdown
133 lines
4.6 KiB
Markdown
# JSON Pointer
|
|
|
|
## Introduction
|
|
|
|
The library supports **JSON Pointer** ([RFC 6901](https://tools.ietf.org/html/rfc6901)) as an alternative means to
|
|
address structured values. A JSON Pointer is a string that identifies a specific value within a JSON document.
|
|
|
|
Consider the following JSON document
|
|
|
|
```json
|
|
{
|
|
"array": ["A", "B", "C"],
|
|
"nested": {
|
|
"one": 1,
|
|
"two": 2,
|
|
"three": [true, false]
|
|
}
|
|
}
|
|
```
|
|
|
|
Then every value inside the JSON document can be identified as follows:
|
|
|
|
| JSON Pointer | JSON value |
|
|
|-------------------|----------------------------------------------------------------------------------|
|
|
| `` | `#!json {"array":["A","B","C"],"nested":{"one":1,"two":2,"three":[true,false]}}` |
|
|
| `/array` | `#!json ["A","B","C"]` |
|
|
| `/array/0` | `#!json A` |
|
|
| `/array/1` | `#!json B` |
|
|
| `/array/2` | `#!json C` |
|
|
| `/nested` | `#!json {"one":1,"two":2,"three":[true,false]}` |
|
|
| `/nested/one` | `#!json 1` |
|
|
| `/nested/two` | `#!json 2` |
|
|
| `/nested/three` | `#!json [true,false]` |
|
|
| `/nested/three/0` | `#!json true` |
|
|
| `/nested/three/1` | `#!json false` |
|
|
|
|
Note `/` does not identify the root (i.e., the whole document), but an object entry with empty key `""`. See
|
|
[RFC 6901](https://tools.ietf.org/html/rfc6901) for more information.
|
|
|
|
## JSON Pointer creation
|
|
|
|
JSON Pointers can be created from a string:
|
|
|
|
```cpp
|
|
json::json_pointer p("/nested/one");
|
|
```
|
|
|
|
Furthermore, a user-defined string literal can be used to achieve the same result:
|
|
|
|
```cpp
|
|
auto p = "/nested/one"_json_pointer;
|
|
```
|
|
|
|
The escaping rules of [RFC 6901](https://tools.ietf.org/html/rfc6901) are implemented. See the
|
|
[constructor documentation](../api/json_pointer/json_pointer.md) for more information.
|
|
|
|
## Value access
|
|
|
|
JSON Pointers can be used in the [`at`](../api/basic_json/at.md), [`operator[]`](../api/basic_json/operator%5B%5D.md),
|
|
and [`value`](../api/basic_json/value.md) functions just like object keys or array indices.
|
|
|
|
```cpp
|
|
// the JSON value from above
|
|
auto j = json::parse(R"({
|
|
"array": ["A", "B", "C"],
|
|
"nested": {
|
|
"one": 1,
|
|
"two": 2,
|
|
"three": [true, false]
|
|
}
|
|
})");
|
|
|
|
// access values
|
|
auto val = j[""_json_pointer]; // {"array":["A","B","C"],...}
|
|
auto val1 = j["/nested/one"_json_pointer]; // 1
|
|
auto val2 = j.at(json::json_pointer("/nested/three/1")); // false
|
|
auto val3 = j.value(json::json_pointer("/nested/four"), 0); // 0
|
|
```
|
|
|
|
!!! note "Creating intermediate levels that don't exist"
|
|
|
|
See the [`operator[]` notes](../api/basic_json/operator%5B%5D.md#return-value) for how array vs. object is
|
|
decided when a pointer creates intermediate levels that don't exist yet.
|
|
|
|
## Flatten / unflatten
|
|
|
|
The library implements a function [`flatten`](../api/basic_json/flatten.md) to convert any JSON document into a JSON
|
|
object where each key is a JSON Pointer and each value is a primitive JSON value (i.e., a string, boolean, number, or
|
|
null).
|
|
|
|
```cpp
|
|
// the JSON value from above
|
|
auto j = json::parse(R"({
|
|
"array": ["A", "B", "C"],
|
|
"nested": {
|
|
"one": 1,
|
|
"two": 2,
|
|
"three": [true, false]
|
|
}
|
|
})");
|
|
|
|
// create flattened value
|
|
auto j_flat = j.flatten();
|
|
```
|
|
|
|
The resulting value `j_flat` is:
|
|
|
|
```json
|
|
{
|
|
"/array/0": "A",
|
|
"/array/1": "B",
|
|
"/array/2": "C",
|
|
"/nested/one": 1,
|
|
"/nested/two": 2,
|
|
"/nested/three/0": true,
|
|
"/nested/three/1": false
|
|
}
|
|
```
|
|
|
|
The reverse function, [`unflatten`](../api/basic_json/unflatten.md) recreates the original value.
|
|
|
|
```cpp
|
|
auto j_original = j_flat.unflatten();
|
|
```
|
|
|
|
## See also
|
|
|
|
- Class [`json_pointer`](../api/json_pointer/index.md)
|
|
- Function [`flatten`](../api/basic_json/flatten.md)
|
|
- Function [`unflatten`](../api/basic_json/unflatten.md)
|
|
- [JSON Patch](json_patch.md) - paths inside a patch are JSON Pointers
|
|
- [JSON Merge Patch](merge_patch.md) - an alternative patch format that does not use JSON Pointer
|