* 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>
4.3 KiB
nlohmann::basic_json::unflatten
basic_json unflatten() const;
The function restores the arbitrary nesting of a JSON value that has been flattened before using the
flatten() function. The JSON value must meet certain constraints:
- The value must be an object.
- The keys must be JSON pointers (see RFC 6901)
- The mapped values must be primitive JSON types.
Return value
the original JSON from a flattened version
Exception safety
Strong exception safety: if an exception occurs, the original value stays intact.
Exceptions
The function can throw the following exceptions:
- Throws
type_error.314if value is not an object - Throws
type_error.315if object values are not primitive - Throws
type_error.313if a key (JSON pointer) leads to a conflicting nesting; example:"invalid value to unflatten" - Throws
parse_error.106if an array index in a key begins with '0'; example:"array index '01' must not begin with '0'" - Throws
parse_error.107if a key is not empty and does not begin with a slash (/); example:"JSON pointer must be empty or begin with '/' - was: 'a'" - Throws
parse_error.108if a tilde (~) in a key is not followed by0or1; example:"escape character '~' must be followed with '0' or '1'" - Throws
parse_error.109if an array index in a key is not a number; example:"array index 'one' is not a number" - Throws
out_of_range.404if a level becomes an array (because one of its keys is0) and another key at that level is empty (as in/a/), is-, or begins with a digit but is not a valid array index (such as1a); examples:"unresolved reference token '-'","unresolved reference token ''"
Complexity
Linear in the size of the JSON value.
Notes
Empty objects and arrays are flattened by flatten() to #!json null values and cannot be unflattened to
their original type.
A flattened array and a flattened object whose keys are array indices are indistinguishable, because both are
described by the same JSON pointers. A value is therefore restored as an array if and only if one of its keys is the
reference token 0, and as an object otherwise: #!json {"2": 1} is restored unchanged, whereas #!json {"0": 1} is
restored as #!json [1]. This decision does not depend on the order in which the flattened object is iterated.
A third case is an object that has the key 0 next to a key that is not a valid array index: #!json {"0": 1, "b": 2}
is flattened to #!json {"/0": 1, "/b": 2}, and unflatten treats the level as an array and throws
parse_error.109 because b is not a number. (For the keys
-, 1a, or the empty key instead of b, it throws out_of_range.404.)
Apart from these three cases, for a JSON value j, the following is always true:
#!cpp j == j.flatten().unflatten().
Examples
??? example
The following code shows how a flattened JSON object is unflattened into the original nested JSON object.
```cpp
--8<-- "examples/unflatten.cpp"
```
Output:
```json
--8<-- "examples/unflatten.output"
```
See also
flatten- the reverse function- JSON Pointer - the article on JSON Pointer and flattening
Version history
- Added in version 2.0.0.
- Made the array/object decision independent of the object's iteration order in version 3.13.0.
- Throws
parse_error.109instead ofout_of_range.404for a one-character array index that is not a digit (e.g.,/x) in version 3.13.0, as it already did for longer ones.