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.

Sign up for GitHub

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

Jump to bottom

Encode.string does not always produce valid JSON #40

Open

travis-leith opened this issue Jan 2, 2021 · 0 comments

travis-leith commented Jan 2, 2021

specifically when the input string contains new lines, tab characters, quote characters etc.

travis-leith mentioned this issue

strings with invalid json characters are now handled correctly #41

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment