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
According the JSON specification, "\0" is not a valid JSON string and must be encoded with four hexadecimal bytes. It's not just a theoretical problem - some python JSON parsers do not accept it.
The BrowserCompatible mode does handle this correctly, but I don't want to escape forward slashes.
Hi. This is quite important to us. I have tried to look at making a patch myself, but this code is fairly complex and I don't want to make a over-reaching change without knowing it would be accepted.
What I don't understand is why the BrowserCompatible code path is so different from the other code path.
According the JSON specification,
"\0"
is not a valid JSON string and must be encoded with four hexadecimal bytes. It's not just a theoretical problem - some python JSON parsers do not accept it.The
BrowserCompatible
mode does handle this correctly, but I don't want to escape forward slashes.I recommend the following unit test:
The text was updated successfully, but these errors were encountered: