amorfo77/json
1
0
Fork 0
mirror of https://github.com/nlohmann/json.git synced 2026-07-28 21:34:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: dfa51af692

Browse Source
This commit is contained in:
nlohmann
2026-07-26 08:34:08 +00:00
parent 45d2de5d9d
commit 17d3b523f9
259 changed files with 564 additions and 508 deletions
Download Patch File Download Diff File Expand all files Collapse all files
api/basic_json/dump/index.html
+2 -2
View File
File diff suppressed because one or more lines are too long
api/basic_json/dump/index.md
+6
View File
@@ -31,6 +31,12 @@ Strong guarantee: if an exception is thrown, there are no changes to any JSON va
Throws [`type_error.316`](https://json.nlohmann.me/home/exceptions/#jsonexceptiontype_error316) if a string stored inside the JSON value is not UTF-8 encoded and `error_handler` is set to `strict`
Serializing untrusted input
When serializing values that may contain invalid or untrusted UTF-8 (e.g., bytes taken directly from network input), `dump()` throws [`type_error.316`](https://json.nlohmann.me/home/exceptions/#jsonexceptiontype_error316) in the default `strict` mode. To serialize such data without throwing, pass [`error_handler_t::replace`](https://json.nlohmann.me/api/basic_json/error_handler_t/index.md) (substitutes U+FFFD) or [`error_handler_t::ignore`](https://json.nlohmann.me/api/basic_json/error_handler_t/index.md). Callers that serialize untrusted input on a crash-sensitive path should either choose a non-strict error handler or wrap `dump()` in a `try`/`catch`.
See the [FAQ](https://json.nlohmann.me/home/faq/#serializing-untrusted-or-invalid-utf-8) for details.
## Complexity
Linear.