* 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>
2.3 KiB
2.3 KiB
std::formatternlohmann::basic_json\
namespace std {
template <>
struct formatter<nlohmann::basic_json, char>;
}
Specialization to make JSON values formattable with std::format
(and the other members of C++20's <format> header, such as std::format_to).
A subset of the standard format spec grammar is
supported, repurposed for JSON pretty-printing; any other spec component (sign, the 0 flag, precision,
L, a dynamic width such as #!cpp "{:{}}", or a trailing type character) throws
std::format_error:
#!cpp "{}"serializes the value the same way asdump()(compact, no whitespace).#!cpp "{:#}"("alternate form") serializes the value the same way as#!cpp dump(4)(pretty-printed with an indent of 4).- A width, with or without
#!cpp "#"(e.g.#!cpp "{:2}"or#!cpp "{:#2}"), serializes the value the same way as#!cpp dump(width)— a width on its own implies pretty-printing, since an indent size has no meaning for compact output. fill-and-align(e.g.#!cpp "{:.>#}"or#!cpp "{:.>3}") picks a custom indent character, the same way as#!cpp dump(indent, indent_char). The alignment direction itself (#!cpp '<',#!cpp '>',#!cpp '^') has no separate meaning for JSON values — only the fill character before it is used, and any of the three directions is accepted.
This specialization is only available for #!cpp char-based JSON values and only if the standard library
provides <format>, controlled by the JSON_HAS_STD_FORMAT macro.
Examples
??? example
The example shows how to format JSON values with `std::format`.
```cpp
--8<-- "examples/std_formatter.c++20.cpp"
```
Output:
```json
--8<-- "examples/std_formatter.c++20.output"
```
See also
dump- serializationoperator<<(std::ostream&)- serialize to streamformat_as- customization point used byfmt::format(fmtlib)- Serialization - the serialization article
Version history
- Added in version 3.13.0.