* 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>
6.0 KiB
nlohmann::basic_json_view::value
// (1)
template<typename T>
T value(string_view_t key, const T& default_value) const;
string_t value(string_view_t key, const char* default_value) const;
// (2)
template<typename T>
T value(const json_pointer& ptr, const T& default_value) const;
string_t value(const json_pointer& ptr, const char* default_value) const;
- Returns the value of the object member with key
key— the first one, should the key occur more than once (see Notes on duplicate keys) — converted toT, ordefault_valueif there is no such member. - Returns the value a JSON pointer
ptrrefers to, starting at this value, converted toT, ordefault_valueifptrcannot be resolved.
Both overloads have a dedicated #!cpp const char* overload, so #!cpp v.value(key, "default") (and the JSON pointer
equivalent) deduce string_t, not const char*, for their return type and for the comparison used to pick between
key and default_value.
Template parameters
T- the type to convert the found value to; also the type of
default_value
Parameters
key(in)- object key of the element to access
ptr(in)- JSON pointer to the element to access
default_value(in)- the value to return if
key/ptrresolves to no value
Return value
- the first member with key
key, converted toT, ordefault_value - the value
ptrresolves to, converted toT, ordefault_value
Exception safety
Strong guarantee: there are no changes to the view or the document it refers to.
Exceptions
- Throws
type_error.306if the value is not an object — the same exception, with the same message, thatBasicJsonType::valuethrows for the same call. If a member with keykeyis found, throws whatever converting it toTthrows (typicallytype_error.302, with the same messageBasicJsonType::valuethrows for the same mismatch); a missing member never throws. - Throws
type_error.306if this value — not the valueptrresolves to — is neither an object nor an array. Throwsparse_error.106orparse_error.109ifptrcontains a malformed array index. Ifptrresolves to a value, throws whatever converting it toTthrows. Every other wayptrcan fail to resolve — a missing key, an out-of-range or "-" array index, an unresolvable token on a primitive — yieldsdefault_valueinstead of throwing, exactly asBasicJsonType::valuecatchesout_of_rangeand returnsdefault_value.
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
operator[], members are compared one after another, in document order, stopping at the first match. Plus the complexity of converting the found member toT(seeget). 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 the number of reference tokens of
ptrand, for each token, in the number of members of the object at that level or the index into the array — as for theoperator[]andatoverloads that take a JSON pointer. Plus the complexity of converting the resolved value toT.
Notes
!!! warning "Duplicate keys: the first member wins"
If the source text repeats a key, this resolves to the *first* member with it, not to the last one that
[`materialize()`](materialize.md) and `parse()` keep. See the [Notes on duplicate keys](operator[].md#notes) of
`operator[]` and [Duplicate keys](../../features/json_view.md#duplicate-keys) for the reasons and for how to get
the last value.
!!! info "Differences to at and operator[]"
Unlike [`at`](at.md), this function does not throw if `key`/`ptr` resolves to no value. Unlike
[`operator[]`](operator[].md), it never returns a [discarded](is_discarded.md) view — it always returns a `T` —
and it is available on any view, since it never needs to insert a missing element the way the non-const
`BasicJsonType::operator[]` would.
!!! info "Which values can be asked"
As for [`BasicJsonType::value`](../basic_json/value.md), the key overload (1) requires an object, and the JSON
pointer overload (2) an object or an array.
Examples
??? example "Example: (1) access specified object element with default value"
The example below reads a couple of optional configuration fields with a default, so that a missing key never
needs a `#!cpp try`/`#!cpp catch` of its own.
```cpp
--8<-- "examples/basic_json_view__value.cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__value.output"
```
??? example "Example: (2) access specified element via JSON pointer with default value"
The example below reads an optional, nested configuration value with a default, given as a JSON pointer.
```cpp
--8<-- "examples/basic_json_view__value_json_pointer.cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__value_json_pointer.output"
```
See also
at- access specified element with bounds checking (throws instead of returning a default value)operator[]- access specified element (returns a discarded view instead of a default value)BasicJsonType::value- the corresponding function ofbasic_json
Version history
- Added in version 3.13.0.