Files
json/docs/mkdocs/docs/api/basic_json_view/dump.md
T
Niels Lohmann 6a852ab96d Split the json_view feature page into sub-pages (#6018)
* Split the json_view feature page into sub-pages

The single features/json_view.md page grew to ~600 lines covering eight
topics. Split it into features/json_view/ with an overview page and
pages for ownership and lifetime, differences from basic_json, reading
values, generic code, editing, and images.

The new differences page collects what was spread over several sections
("What is the same", "What is different", "Duplicate keys", and notes in
the conversion and serialization sections) under one summary table, and
adds the parts of the basic_json interface a view does not have. The
other pages now link to it instead of restating the rules.

Internal links across the documentation point to the new pages.

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

* Docs: fix stale comments and trim repeated text in json_view pages

- fig-jsonview.js/.css: point the header comments at the new pages
- reading.md: views' strings are valid as long as the document (and a
  borrowed source text), as lifetime.md says
- reading.md, generic_code.md: link to differences.md instead of
  restating the member-order and repeated-key rules
- differences.md: drop the third mention of ordering comparisons, name
  rbegin()/rend() in the iterator row
- exceptions.md: link editable documents to editing.md

Signed-off-by: Niels Lohmann <mail@nlohmann.me>

---------

Signed-off-by: Niels Lohmann <mail@nlohmann.me>
2026-11-09 08:12:00 +01:00

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 indent is nonnegative, array elements and object members are pretty-printed with that indent level. An indent level of 0 only inserts newlines. -1 (the default) selects the most compact representation.
indent_char (in)
The character used for indentation if indent is greater than 0. The default is (space).
ensure_ascii (in)
If ensure_ascii is #!cpp true, all non-ASCII characters in the output are escaped with \uXXXX sequences, and the result consists of ASCII characters only.
numbers (in)
how to write numbers, see number_format: shortest (the default) writes them the way BasicJsonType::dump would; source copies 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

Version history

  • Added in version 3.13.0.