* 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>
120 lines
4.8 KiB
Markdown
120 lines
4.8 KiB
Markdown
# Specializing enum conversion
|
|
|
|
By default, enum values are serialized to JSON as integers. In some cases, this could result in undesired behavior. If
|
|
the integer values of any enum values are changed after data using those enum values has been serialized to JSON, then
|
|
deserializing that JSON would result in a different enum value being restored, or the value not being found at all.
|
|
|
|
It is possible to more precisely specify how a given enum is mapped to and from JSON as shown below:
|
|
|
|
```cpp
|
|
// example enum type declaration
|
|
enum TaskState {
|
|
TS_STOPPED,
|
|
TS_RUNNING,
|
|
TS_COMPLETED,
|
|
TS_INVALID=-1,
|
|
};
|
|
|
|
// map TaskState values to JSON as strings
|
|
NLOHMANN_JSON_SERIALIZE_ENUM( TaskState, {
|
|
{TS_INVALID, nullptr},
|
|
{TS_STOPPED, "stopped"},
|
|
{TS_RUNNING, "running"},
|
|
{TS_COMPLETED, "completed"},
|
|
})
|
|
```
|
|
|
|
The [`NLOHMANN_JSON_SERIALIZE_ENUM()` macro](../api/macros/nlohmann_json_serialize_enum.md) declares a set of
|
|
`to_json()` / `from_json()` functions for type `TaskState` while avoiding repetition and boilerplate serialization code.
|
|
|
|
## Usage
|
|
|
|
Serialization converts an enum value to its mapped string, deserialization does the reverse, and an unrecognized JSON
|
|
value deserializes to the first pair in the map:
|
|
|
|
```cpp
|
|
// enum to JSON as string
|
|
json j = TS_STOPPED;
|
|
assert(j == "stopped");
|
|
|
|
// json string to enum
|
|
json j3 = "running";
|
|
assert(j3.get<TaskState>() == TS_RUNNING);
|
|
|
|
// undefined json value to enum (where the first map entry above is the default)
|
|
json jPi = 3.14;
|
|
assert(jPi.get<TaskState>() == TS_INVALID );
|
|
```
|
|
|
|
??? example "Example: serializing/deserializing enums, including a second enum type"
|
|
|
|
```cpp
|
|
--8<-- "examples/nlohmann_json_serialize_enum.cpp"
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
--8<-- "examples/nlohmann_json_serialize_enum.output"
|
|
```
|
|
|
|
## Maps with enum keys
|
|
|
|
By default, maps with enum keys, such as `std::map<TaskState, std::string>`, are stored as arrays of `[key, value]`
|
|
pairs, because JSON object keys must be strings. Define
|
|
[`JSON_USE_OBJECTS_FOR_ENUM_KEYED_MAPS`](../api/macros/json_use_objects_for_enum_keyed_maps.md) before including the
|
|
library to store them as objects, with the keys converted by the enum's `to_json()` function:
|
|
|
|
```cpp
|
|
std::map<TaskState, std::string> m = {{TS_STOPPED, "aa"}, {TS_COMPLETED, "bb"}};
|
|
|
|
json j = m;
|
|
// default: [["stopped","aa"],["completed","bb"]]
|
|
// with JSON_USE_OBJECTS_FOR_ENUM_KEYED_MAPS: {"completed":"bb","stopped":"aa"}
|
|
```
|
|
|
|
Either form can be read back, with or without the macro.
|
|
|
|
## Notes
|
|
|
|
Just as in [Arbitrary Type Conversions](arbitrary_types.md) above,
|
|
|
|
- [`NLOHMANN_JSON_SERIALIZE_ENUM()`](../api/macros/nlohmann_json_serialize_enum.md) MUST be declared in your enum type's
|
|
namespace (which can be the global namespace), or the library will not be able to locate it, and it will default to
|
|
integer serialization.
|
|
- It MUST be available (e.g., proper headers must be included) everywhere you use the conversions.
|
|
|
|
Other Important points:
|
|
|
|
- When using [`get<ENUM_TYPE>()`](../api/basic_json/get.md), undefined JSON values will default to the first pair
|
|
specified in your map. Select this default pair carefully. If you desire an exception in this circumstance use
|
|
[`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT()`](../api/macros/nlohmann_json_serialize_enum_strict.md) which behaves
|
|
identically except for throwing an
|
|
[`out_of_range.410`](../home/exceptions.md#jsonexceptionout_of_range410) exception on unrecognized values, both when
|
|
serializing an enum value not listed in the map and when deserializing a JSON value that matches none of the map's
|
|
entries.
|
|
- If an enum or JSON value is specified more than once in your map, the first matching occurrence from the top of the
|
|
map will be returned when converting to or from JSON.
|
|
- To disable the default serialization of enumerators as integers and force a compiler error instead, see [`JSON_DISABLE_ENUM_SERIALIZATION`](../api/macros/json_disable_enum_serialization.md).
|
|
|
|
??? example "Example: `NLOHMANN_JSON_SERIALIZE_ENUM_STRICT` throwing on unrecognized values"
|
|
|
|
```cpp
|
|
--8<-- "examples/nlohmann_json_serialize_enum_strict_err.cpp"
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
--8<-- "examples/nlohmann_json_serialize_enum_strict_err.output"
|
|
```
|
|
|
|
## See also
|
|
|
|
- [Arbitrary Type Conversions](arbitrary_types.md) - convert your own types
|
|
- [Converting values](conversions.md) - the general overview of `get`/`get_to`
|
|
- [`NLOHMANN_JSON_SERIALIZE_ENUM`](../api/macros/nlohmann_json_serialize_enum.md) - define the enum-to-JSON mapping
|
|
- [`NLOHMANN_JSON_SERIALIZE_ENUM_STRICT`](../api/macros/nlohmann_json_serialize_enum_strict.md) - throw on unmapped values
|
|
- [`JSON_DISABLE_ENUM_SERIALIZATION`](../api/macros/json_disable_enum_serialization.md) - disable the default enum conversion
|
|
- [`JSON_USE_OBJECTS_FOR_ENUM_KEYED_MAPS`](../api/macros/json_use_objects_for_enum_keyed_maps.md) - serialize maps with enum keys as objects
|