You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. First of all, thanks for the great job you performed all this time. Your tool turned out to be very helpful for me.
My question is: is there any endline symbols support planning in the near future or it violates standard json formatting rules?
For example, this code will crash the framework (C++):
Therefore, you get a parse error. In version 3.0.0, the error description will be a bit more explanatory:
[json.exception.parse_error.101] parse error at 7: syntax error - invalid string: control character must be escaped; last read: '"test<U+000A>'; expected string literal
Hi. First of all, thanks for the great job you performed all this time. Your tool turned out to be very helpful for me.
My question is: is there any endline symbols support planning in the near future or it violates standard json formatting rules?
For example, this code will crash the framework (C++):
string valueJSON = "{\"test\n\":[1,2,3]}"; json j = json::parse(valueJSON);
with an error: std::invalid_argument: parse error - unexpected '"'; expected string literal
and without \n the parser works ok.
Thanks.
Miroslav
The text was updated successfully, but these errors were encountered: