* 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.9 KiB
nlohmann::basic_json_view::dump
string_t dump(const int indent = -1,
const char indent_char = ' ',
const bool ensure_ascii = false,
const number_format numbers = number_format::shortest) const;
Serializes this value (and its subtree) directly from the flat index, without ever building a BasicJsonType value
first. With the default #!cpp numbers == number_format::shortest, the result is the same string
BasicJsonType::dump would produce for the value
BasicJsonType::parse() builds from the same source text, called with the same indent,
indent_char, and ensure_ascii — except that members of an object appear in document order rather than sorted by
key, and every occurrence of a repeated key is written rather than only the last one (see
Notes on duplicate keys). For a json_view (whose BasicJsonType is not ordered), this means
dump() can print an object's members in a different order than materialize().dump() of the
same subtree.
Parameters
indent(in)- If
indentis nonnegative, array elements and object members are pretty-printed with that indent level. An indent level of0only inserts newlines.-1(the default) selects the most compact representation. indent_char(in)- The character used for indentation if
indentis greater than0. The default is(space). ensure_ascii(in)- If
ensure_asciiis#!cpp true, all non-ASCII characters in the output are escaped with\uXXXXsequences, and the result consists of ASCII characters only. numbers(in)- how to write numbers, see
number_format:shortest(the default) writes them the wayBasicJsonType::dumpwould;sourcecopies every number exactly as it appears in the source text.
Return value
string containing the serialization of this value, or #!cpp "<discarded>" if the view is
discarded.
Exception safety
Strong exception safety: if an exception is thrown, there are no changes to the view or the document it refers to.
Exceptions
May throw #!cpp std::bad_alloc if allocating the output string fails. Unlike
BasicJsonType::dump, there is no error_handler parameter and no
type_error.316: the view only ever holds text the parser
already validated as UTF-8, so there is nothing to replace or ignore.
Complexity
Linear in the size of the output text.
Notes
The walk over the subtree is iterative, so the nesting depth it can write is limited by available memory only, not by
the call stack — as for materialize().
Strings are escaped by the same rules as BasicJsonType::dump.
With #!cpp numbers == number_format::shortest, floats are written with the library's shortest round-trip conversion,
exactly as BasicJsonType::dump would (e.g. #!cpp 1.5, #!cpp 100.0, #!cpp 1e+100), and
integers are copied from the source text — already canonical in JSON, so this matches their shortest form too —
except that #!cpp -0 is written as #!cpp 0, the way BasicJsonType::parse() reads it.
#!cpp number_format::source copies every number exactly as written in the source text instead, with no exception
for #!cpp -0 — #!cpp 1.50, #!cpp 1E2, #!cpp -0.0, #!cpp -0, or all digits of an integer literal with more
digits than any number type holds (such a literal is itself classified as a float, see
What is different) — something BasicJsonType cannot do, since
parsing already reduces every number to its parsed value.
Examples
??? example
The example below forwards a single record out of a larger batch, and re-serializes a configuration file, both
without ever building a `BasicJsonType` value for the surrounding array or for the parts of it that were not
needed. It also shows that [`materialize()`](materialize.md)`.dump()` of the configuration sorts its keys, where
`dump()` on the view keeps the order they appear in the source text.
```cpp
--8<-- "examples/basic_json_view__dump.cpp"
```
Output:
```json
--8<-- "examples/basic_json_view__dump.output"
```
See also
number_format- howdump()writes numbersoperator<<- serialize this value to a streammaterialize- build aBasicJsonTypevalue, e.g. to useBasicJsonType::dump'serror_handlerBasicJsonType::dump- the corresponding function ofbasic_json- Zero-copy JSON views - writing a view back without building a tree
Version history
- Added in version 3.13.0.