mirror of
https://github.com/nlohmann/json.git
synced 2026-11-09 22:12:32 +00:00
* 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>
1.3 KiB
1.3 KiB
nlohmann::ordered_json_document
Defined in header <nlohmann/json_view.hpp>
using ordered_json_document = basic_json_document<ordered_json, view_mode::read_only>;
This type is a basic_json_document of the ordered_json
specialization: materialize() on one of its views preserves the insertion order
of object keys, instead of sorting them like json_document does.
Examples
??? example
The example below demonstrates how `ordered_json_document` preserves the insertion order of object keys when
materializing.
```cpp
--8<-- "examples/ordered_json_document.cpp"
```
Output:
```json
--8<-- "examples/ordered_json_document.output"
```
See also
ordered_json_view- a view of a value of anordered_json_documentjson_document- the corresponding document for the defaultjsonspecialization- Object Order - preserving the insertion order of object keys
- Zero-copy JSON views - how to parse, inspect and edit a document without building a tree
Version history
Added in version 3.13.0.