* 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>
107 lines
4.4 KiB
Markdown
107 lines
4.4 KiB
Markdown
# <small>nlohmann::basic_json::</small>dump
|
|
|
|
```cpp
|
|
string_t dump(const int indent = -1,
|
|
const char indent_char = ' ',
|
|
const bool ensure_ascii = false,
|
|
const error_handler_t error_handler = error_handler_t::strict) const;
|
|
```
|
|
|
|
Serialization function for JSON values. The function tries to mimic Python's
|
|
[`json.dumps()` function](https://docs.python.org/2/library/json.html#json.dump), and currently supports its `indent`
|
|
and `ensure_ascii` parameters.
|
|
|
|
## Parameters
|
|
|
|
`indent` (in)
|
|
: If `indent` is nonnegative, then array elements and object members will be pretty-printed with that indent level. An
|
|
indent level of `0` will only insert newlines. `-1` (the default) selects the most compact representation.
|
|
|
|
`indent_char` (in)
|
|
: The character to use for indentation if `indent` is greater than `0`. The default is ` ` (space).
|
|
|
|
`ensure_ascii` (in)
|
|
: If `ensure_ascii` is true, all non-ASCII characters in the output are escaped with `\uXXXX` sequences, and the
|
|
result consists of ASCII characters only.
|
|
|
|
`error_handler` (in)
|
|
: how to react on decoding errors; there are four possible values (see [`error_handler_t`](error_handler_t.md):
|
|
`strict` (throws an exception in case a decoding error occurs; default), `replace` (replace invalid UTF-8 sequences
|
|
with U+FFFD), `ignore` (ignore invalid UTF-8 sequences during serialization; all valid bytes are copied to the
|
|
output unchanged, and invalid bytes are dropped), and `keep` (write the ill-formed bytes to the output as is,
|
|
without escaping them, even if `ensure_ascii` is `#!cpp true`; the result is then not valid UTF-8, but equals the
|
|
input bytes exactly, and well-formed characters around the ill-formed bytes are still escaped as usual)).
|
|
|
|
## Return value
|
|
|
|
string containing the serialization of the JSON value
|
|
|
|
## Exception safety
|
|
|
|
Strong guarantee: if an exception is thrown, there are no changes to any JSON value.
|
|
|
|
## Exceptions
|
|
|
|
Throws [`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) if a string stored inside the JSON value
|
|
is not UTF-8 encoded and `error_handler` is set to `strict`
|
|
|
|
!!! warning "Serializing untrusted input"
|
|
|
|
When serializing values that may contain invalid or untrusted UTF-8 (e.g., bytes taken directly from network
|
|
input), `dump()` throws [`type_error.316`](../../home/exceptions.md#jsonexceptiontype_error316) in the default
|
|
`strict` mode. To serialize such data without throwing, pass
|
|
[`error_handler_t::replace`](error_handler_t.md) (substitutes U+FFFD) or
|
|
[`error_handler_t::ignore`](error_handler_t.md). Callers that serialize untrusted input on a crash-sensitive path
|
|
should either choose a non-strict error handler or wrap `dump()` in a `#!cpp try`/`#!cpp catch`.
|
|
|
|
See the [FAQ](../../home/faq.md#serializing-untrusted-or-invalid-utf-8) for details.
|
|
|
|
## Complexity
|
|
|
|
Linear.
|
|
|
|
## Notes
|
|
|
|
Floating-point numbers are written with the fewest digits that read back as the same value (for `#!cpp double`; see
|
|
[number handling](../../features/types/number_handling.md#number-serialization)).
|
|
|
|
Binary values are serialized as an object containing two keys:
|
|
|
|
- "bytes": an array of bytes as integers
|
|
- "subtype": the subtype as integer or `#!json null` if the binary has no subtype
|
|
|
|
## Examples
|
|
|
|
??? example
|
|
|
|
The following example shows the effect of different `indent`, `indent_char`, and `ensure_ascii` parameters to the
|
|
result of the serialization.
|
|
|
|
```cpp
|
|
--8<-- "examples/dump.cpp"
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
--8<-- "examples/dump.output"
|
|
```
|
|
|
|
## See also
|
|
|
|
- [`to_string`](to_string.md) - returns a string representation of a JSON value
|
|
- [`operator<<`](../operator_ltlt.md) - serialize to stream
|
|
- [`basic_json_view::dump`](../basic_json_view/dump.md) - the corresponding function of `basic_json_view`, serializing
|
|
directly from a flat index without building a `basic_json` value
|
|
- [Serialization](../../features/serialization.md) - the serialization article
|
|
|
|
## Version history
|
|
|
|
- Added in version 1.0.0.
|
|
- Indentation character `indent_char`, option `ensure_ascii` and exceptions added in version 3.0.0.
|
|
- Error handlers added in version 3.4.0.
|
|
- Serialization of binary values added in version 3.8.0.
|
|
- Error handler `keep` added in version 3.13.0.
|
|
- Doubles are written with the shortest digits (Żmij instead of Grisu2) since version 3.13.0; about 0.1% of doubles are
|
|
written differently, most of them with fewer digits.
|