* Review and extend the documentation, and check it in CI A review of all documentation pages found factual errors, dead links, missing cross-references, and gaps in examples. This fixes them and adds checks so the same problems are caught automatically. Fixes: - wrong signatures and version histories (operator!= C++20 member, binary() subtype type, get<PointerType>(), JSON_NO_THREAD_LOCAL, ...) - stale descriptions (number parsing since #5283, UBJSON table, SAX example that no longer compiled, tsl::ordered_map advice) - dead internal and external links; repology.org badges (the domain is suspended) replaced by badges that query the registries directly - deprecation notes link the migration guide; the guide itself fixed Additions: - "See also" sections, cross-references, 25 runnable examples, 12 Mermaid diagrams, new API pages for json_pointer::operator<=> and byte_container_with_subtype::operator==/!= - landing page, guides for untrusted input and performance - "unreleased" badge after versions newer than the latest release Checks: - strict documentation build (broken links/anchors fail it); CI and the publish workflow fetch the full history the build needs - weekly external link check, Mermaid syntax check in CI - check_structure.py: example titles, heading levels, alt texts, header links, docset index coverage; its unused-example check works again - all examples produce the same output on every platform Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Keep the customer links that could not be fixed A dead link on the customers page is still the evidence of where the use of the library was documented. Keep the original URLs of the entries without a working replacement (Marne, Cisco Webex Desk Camera, Philips Hue, CyberArk) and exclude exactly these URLs from the link check. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct the duplicate-key recipe's claim about SAX positions The SAX interface's key() receives no position either; only parse_error() does. Also note that the recipe does not report the path to the repeated key (see discussion #5085). Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Say the library is available as a single header and mention json_fwd.hpp Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Correct documentation errors found while hunting for bugs - patch/patch_inplace: list the JSON pointer errors parse_error.106-109 and out_of_range.402/404, and quote the actual parse_error.105 message. - unflatten: list parse_error.106/107/108 and out_of_range.404. - to_bson: list out_of_range.415 (binary subtype above 255) and note that 412 and 415 are new in 3.13.0. - to_string: state that string_t must be convertible to std::string, also in the StringType requirements table. - JSON Lines: a `while (input >> j)` loop also throws after the last value for concatenated JSON values; show a loop that works for both. - BON8: a string gets 0xFF only if nothing follows it in the message; a string at the end of an array or object is ended by 0xFE. - custom_string_type.hpp: add operator+=(char), which the "Always required" list asks for (json_pointer::to_string, flatten, unflatten, and diff did not compile), and an ADL int_to_string for diff and items. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * Cache the release headers with functools.lru_cache Codacy (Pylint) flagged the mutable default argument that header() used as its cache. functools.lru_cache keeps the same memoization without it. The script's output is unchanged. Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>
8.9 KiB
Migration Guide
This page collects some guidelines on how to future-proof your code for future versions of this library. For how to add the library to your project in the first place, see Integration, CMake, or Package Managers.
Replace deprecated functions
The following functions have been deprecated and will be removed in the next major version (i.e., 4.0.0). All
deprecations are annotated with
HEDLEY_DEPRECATED_FOR to report which
function to use instead.
Parsing
-
Function
friend std::istream& operator<<(basic_json&, std::istream&)is deprecated since 3.0.0. Please usefriend std::istream& operator>>(std::istream&, basic_json&)instead.=== "Deprecated"
```cpp nlohmann::json j; std::stringstream ss("[1,2,3]"); j << ss; ```=== "Future-proof"
```cpp nlohmann::json j; std::stringstream ss("[1,2,3]"); ss >> j; ``` -
Passing iterator pairs or pointer/length pairs to parsing functions (
parse,accept,sax_parse,from_cbor,from_msgpack,from_ubjson, andfrom_bson) via initializer lists is deprecated since 3.8.0. Instead, pass two iterators; for instance, callfrom_cbor(ptr, ptr+len)instead offrom_cbor({ptr, len}). Likewise, passing a pointer and a length as two separate arguments tofrom_cbor,from_msgpack,from_ubjson, andfrom_bsonis deprecated since 3.8.0; callfrom_cbor(ptr, ptr+len)instead offrom_cbor(ptr, len).=== "Deprecated"
```cpp const char* s = "[1,2,3]"; bool ok = nlohmann::json::accept({s, s + std::strlen(s)}); ```=== "Future-proof"
```cpp const char* s = "[1,2,3]"; bool ok = nlohmann::json::accept(s, s + std::strlen(s)); ```
JSON Pointers
-
Comparing JSON Pointers with strings via
operator==andoperator!=is deprecated since 3.11.2. To compare ajson_pointerpwith a strings, convertsto ajson_pointerfirst and usejson_pointer::operator==orjson_pointer::operator!=.=== "Deprecated"
```cpp nlohmann::json::json_pointer lhs("/foo/bar/1"); assert(lhs == "/foo/bar/1"); ```=== "Future-proof"
```cpp nlohmann::json::json_pointer lhs("/foo/bar/1"); assert(lhs == nlohmann::json::json_pointer("/foo/bar/1")); ``` -
The implicit conversion from JSON Pointers to string (
json_pointer::operator string_t) is deprecated since 3.11.0. Usejson_pointer::to_stringinstead.=== "Deprecated"
```cpp nlohmann::json::json_pointer ptr("/foo/bar/1"); std::string s = ptr; ```=== "Future-proof"
```cpp nlohmann::json::json_pointer ptr("/foo/bar/1"); std::string s = ptr.to_string(); ``` -
Passing a
basic_jsonspecialization as template parameterRefStringTypetojson_pointeris deprecated since 3.11.0. The string type can now be directly provided. This also applies to passing such a JSON pointer toat,contains,operator[], andvalue.=== "Deprecated"
```cpp using my_json = nlohmann::basic_json<std::map, std::vector, my_string_type>; nlohmann::json_pointer<my_json> ptr("/foo/bar/1"); ```=== "Future-proof"
```cpp nlohmann::json_pointer<my_string_type> ptr("/foo/bar/1"); ```Thereby,
my_json::json_pointeris an alias fornlohmann::json_pointer<my_string_type>; in general,basic_json::json_pointeris always an alias to thejson_pointerwith the appropriate string type for all specializations ofbasic_json.
Miscellaneous functions
-
The function
iterator_wrapperis deprecated since 3.1.0. Please use the member functionitemsinstead.=== "Deprecated"
```cpp for (auto &x : nlohmann::json::iterator_wrapper(j)) { std::cout << x.key() << ":" << x.value() << std::endl; } ```=== "Future-proof"
```cpp for (auto &x : j.items()) { std::cout << x.key() << ":" << x.value() << std::endl; } ``` -
Function
friend std::ostream& operator>>(const basic_json&, std::ostream&)is deprecated since 3.0.0. Please usefriend operator<<(std::ostream&, const basic_json&)instead.=== "Deprecated"
```cpp j >> std::cout; ```=== "Future-proof"
```cpp std::cout << j; ``` -
The legacy comparison behavior for discarded values is deprecated since 3.11.0. It is already disabled by default and can still be enabled by defining
JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISONto1.=== "Deprecated"
```cpp #define JSON_USE_LEGACY_DISCARDED_VALUE_COMPARISON 1 #include <nlohmann/json.hpp> ```=== "Future-proof"
```cpp #include <nlohmann/json.hpp> ```
Replace implicit conversions
Implicit conversions via operator ValueType will be switched off by default
in the next major release of the library.
You can prepare existing code by already defining
JSON_USE_IMPLICIT_CONVERSIONS to 0 and replace any implicit
conversions with calls to get, get_to,
get_ref, or get_ptr.
!!! tip "Automatic migration"
The community-maintained clang-tidy check `modernize-nlohmann-json-explicit-conversions` rewrites most implicit
conversions into calls to [`get`](../api/basic_json/get.md). It is not part of clang-tidy itself; see
[discussion #4610](https://github.com/nlohmann/json/discussions/4610) for how to build and use it.
=== "Deprecated"
```cpp
nlohmann::json j = "Hello, world!";
std::string s = j;
```
=== "Future-proof"
```cpp
nlohmann::json j = "Hello, world!";
auto s = j.get<std::string>();
```
=== "Future-proof (alternative)"
```cpp
nlohmann::json j = "Hello, world!";
std::string s;
j.get_to(s);
```
Import namespace literals for UDLs
The user-defined string literals operator""_json and
operator""_json_pointer will be removed from the global namespace in the
next major release of the library.
=== "Deprecated"
```cpp
nlohmann::json j = "[1,2,3]"_json;
```
=== "Future-proof"
```cpp
using namespace nlohmann::literals;
nlohmann::json j = "[1,2,3]"_json;
```
To prepare existing code, define JSON_USE_GLOBAL_UDLS to 0 and bring the
string literals into scope where needed.
Do not hard-code the complete library namespace
The nlohmann namespace contains a sub-namespace to avoid problems when different
versions or configurations of the library are used in the same project. Always use nlohmann as namespace or, when the
exact version and configuration is relevant, use macro
NLOHMANN_JSON_NAMESPACE to denote the namespace.
=== "Dangerous"
```cpp
void to_json(nlohmann::json_abi_v3_11_2::json& j, const person& p)
{
j["age"] = p.age;
}
```
=== "Future-proof"
```cpp
void to_json(nlohmann::json& j, const person& p)
{
j["age"] = p.age;
}
```
=== "Future-proof (alternative)"
```cpp
void to_json(NLOHMANN_JSON_NAMESPACE::json& j, const person& p)
{
j["age"] = p.age;
}
```
Do not use the detail namespace
The nlohmann::detail namespace is not part of the public API of the library and can change in any version without
an announcement. Do not rely on any function or type in the detail namespace.