* 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>
2.0 KiB
2.0 KiB
nlohmann::ordered_json_editable_document
Defined in header <nlohmann/json_view.hpp>
using ordered_json_editable_document = basic_json_document<ordered_json, view_mode::editable>;
This type is an editable basic_json_document of the
ordered_json specialization: set and
push_back change values after parsing, as for
json_editable_document, and
materialize() preserves the document order of object members — including
members set added — instead of sorting them like
json_editable_document does.
Examples
??? example
The example below edits a document with `set`, then shows that `materialize()` keeps the member order of the
source text (with the new member at the end) for `ordered_json_editable_document`, where it would sort the
members alphabetically for [`json_editable_document`](json_editable_document.md).
```cpp
--8<-- "examples/ordered_json_editable_document.cpp"
```
Output:
```json
--8<-- "examples/ordered_json_editable_document.output"
```
See also
ordered_json_editable_view- a view of a value of anordered_json_editable_documentordered_json_document- the read-only document this type adds edits tojson_editable_document- the corresponding editable document for the defaultjsonspecialization- Object Order - preserving the insertion order of object keys
- Edits - what an edit guarantees
- Zero-copy JSON views - editing a document in place and writing it back
Version history
Added in version 3.13.0.