-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
escapeString compatibility with encoding/json #87
base: master
Are you sure you want to change the base?
Conversation
and `encoding/json` from standard library
it is in range 0x23-0x5B see page 8 of: https://www.rfc-editor.org/rfc/rfc8259.html this should not be a problem though, if the unescape is applied to properly escaped json data
This reverts commit 7a86309.
This seems a valid fix...@valyala do you think this can be merged? |
@barkyq could you add tests? |
Tests for string escape conformance with standard lib
I've added tests in aperturerobotics#2 -- since this repo doesn't seem to be merging PRs in last few years I'm hopeful that it could be merged in this other recent fork (https://github.com/aperturerobotics/fastjson/ - no affiliation). I'd be just as happy seeing these changes merged here too. The lack of proper string escaping can pretty seriously break using serialized JSON when sending it to other systems that are not as forgiving with input characters. |
Tests for string escape conformance with standard lib
Edited parser.go to escape strings according to RFC8259