JSON string encoding as defined in RFC8529 / ECMA 404 is not correct/complete in Clixon.
More specifically, escaping using backslash \ is made unconditionally in current versions
For example, decoding JSON string: "\n" becomes "n", which is not correct.
JSON string encoding as defined in RFC8529 / ECMA 404 is not correct/complete in Clixon. More specifically, escaping using backslash \ is made unconditionally in current versions For example, decoding JSON string: "\n" becomes "n", which is not correct.