* 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>
9.5 KiB
nlohmann::basic_json_view::operator[]
// (1)
basic_json_view operator[](string_view_t key) const;
basic_json_view operator[](const char* key) const;
basic_json_view operator[](const string_t& key) const;
// (2)
basic_json_view operator[](size_type idx) const;
template<typename IntegerType>
basic_json_view operator[](IntegerType idx) const;
// (3)
basic_json_view operator[](const json_pointer& ptr) const;
- Returns the value of the object member with key
key— the first one, should the key occur more than once (see the Notes below) — or a discarded view if there is no such member. - Returns the array element at index
idx, or a discarded view ifidxis out of range. The template accepts every integer type except#!cpp booland#!cpp std::size_t(#!cpp int,#!cpp unsigned,#!cpp long,#!cpp std::int64_t, ...) and forwards to thesize_typeoverload, so that an integer argument is not ambiguous between that overload and 1; a negativeidxis out of range. - Returns the value a JSON pointer
ptrrefers to, starting at this value, or a discarded view wherever resolving it further is not possible without inserting into or extending the document (see Return value and Exceptions below).
Parameters
key(in)- object key of the element to access
idx(in)- index of the element to access
ptr(in)- JSON pointer to the element to access
Return value
- the value of the first member with key
key, or a discarded view if no member has this key (or if this view is discarded) - the element at index
idx, or a discarded view if#!cpp idx >= size()oridxis negative (or if this view is discarded) - the value
ptrresolves to, starting at this value, or a discarded view (also if this view is discarded) for exactly the reference tokens where the const overload ofBasicJsonType::operator[]invokes undefined behavior for the same pointer and the same document: an object member that does not exist, or an array index that is out of range
Exception safety
Strong guarantee: there are no changes to the view or the document it refers to.
Exceptions
- Throws
type_error.305if the value is not an object and not discarded — the same exception, with the same message, that the const overload ofBasicJsonType::operator[]throws for a string argument on a non-object value. - Throws
type_error.305if the value is not an array and not discarded — the same exception, with the same message, that the const overload ofBasicJsonType::operator[]throws for a numeric argument on a non-array value. - Throws the same exceptions, with the same messages, that the const overload of
BasicJsonType::operator[]throws for the same pointer and the same document:out_of_range.402if a reference token is#!cpp "-"at an array.out_of_range.404if a reference token cannot be resolved because it is used on a primitive value.parse_error.106if an array index inptrbegins with#!cpp '0'.parse_error.109if an array index inptris not a number.
None of these exceptions carry a JSON_DIAGNOSTICS path: the view has no
BasicJsonType value to point at, so the exception is created without one, even if BasicJsonType was built with
JSON_DIAGNOSTICS enabled.
Complexity
- Linear in the number of members: as for
ordered_json, members are compared one after another, in document order, stopping at the first match. Each comparison first checks the key's length — already known from the index, without reading the key bytes — before comparing its content, so a key of a different length thankeyis rejected without touching the source text. Objects with 128 or more members get a hash index of their keys while parsing, so that a lookup in them takes constant time on average. - Linear in
idx: elements are skipped one at a time from the first one, since they are not a fixed size in the index (unlikeBasicJsonType's array, which is random-access). Constant if no element of the array is an array or object, since the elements are then adjacent in the index. - Linear in the number of reference tokens of
ptrand, for each token, in the number of members of the object at that level (as 1.) or the index into the array (as 2.).
Notes
Unlike BasicJsonType::operator[], which is undefined behavior (guarded by a
runtime assertion) for a missing key on a const value, this operator returns a
safe, testable result for a missing key or an index out of range: a discarded view, which is
tested with is_discarded.
There is also no non-const overload that inserts a missing key or extends an array — a view never modifies the
document.
!!! info "Chained access"
`#!cpp operator[]` on a [discarded](is_discarded.md) view returns a discarded view and does not throw, so a chain
like `#!cpp v["a"]["b"][0]` is safe even if `"a"` or `"b"` is missing: the first missing step makes the whole
result discarded, which is tested once at the end. Type errors on values that are *not* discarded still throw: a
key on an array or a primitive, or an index on an object or a primitive, is `type_error.305` as for
`BasicJsonType`. [`at`](at.md) still throws for a discarded view, as it does for a missing key.
!!! warning "Duplicate keys: the first member wins"
If the source text has an object with a duplicate key, `#!cpp operator[]` (and [`at`](at.md), [`find`](find.md),
[`contains`](contains.md), [`value`](value.md), and JSON pointer resolution) all resolve to
the *first* member with that key, because a lookup can stop as soon as it finds a match. This is different from
[`materialize()`](materialize.md) (and [`BasicJsonType::parse()`](../basic_json/parse.md)), which replay every
member in order and so keep the *last* value for a repeated key, so `#!cpp v["a"]` and
`#!cpp v.materialize()["a"]` can differ. To get the value `parse()` would give, use
[`materialize()`](materialize.md) or iterate the members with [`items()`](items.md) and keep the last match.
The key hash index of a larger object (128 members or more) leads to the first member of a key as well.
[`begin()`](begin.md)/[`end()`](end.md) and [`items()`](items.md) iterate over *all* members, including
duplicates, in document order. See [Duplicate keys](../../features/json_view.md#duplicate-keys) and
[`size()`](size.md#notes).
!!! info "JSON pointer resolution"
Overload 3 walks `ptr` one reference token at a time, starting at this value, the same way [`at`](at.md) and
[`contains`](contains.md) do. It only ever returns a discarded view where the **const** overload of
`BasicJsonType::operator[]` would be undefined behavior for the same pointer — a missing object member or an
out-of-range array index — and still throws for every other way `ptr` can fail to resolve. See
[`at`](at.md#exceptions) for the checked version, which throws in every case instead, and
[`contains`](contains.md) for a version that never throws.
Examples
??? example "Example: (1)/(2) access specified element"
The example below reads a couple of fields out of a batch of user records without ever materializing a full
`BasicJsonType` value for the batch. `operator[]` is used both to look up an optional object member and to index
into an array — in both cases, a missing value comes back as a discarded view that can be tested with a plain
`#!cpp if`, instead of relying on undefined behavior.
```cpp
--8<-- "examples/basic_json_view__operator[].cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__operator[].output"
```
??? example "Example: (3) access specified element via JSON pointer"
The example below reaches straight into one deeply nested field of a large document with a single JSON pointer,
without ever building a tree for the rest of it, and shows the discarded-view and throwing outcomes of a pointer
that cannot be fully resolved.
```cpp
--8<-- "examples/basic_json_view__operator[]_json_pointer.cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__operator[]_json_pointer.output"
```
See also
at- access specified element with bounds checking (throws instead of returning a discarded view)front,back- access the first or last elementfind,contains- look up a member without throwingBasicJsonType::operator[]- the corresponding function ofbasic_jsonjson_pointer- JSON pointer type used by overload 3
Version history
- Added in version 3.13.0.