-
Notifications
You must be signed in to change notification settings - Fork 10
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
String should not contain control characters. #31
Comments
I met this issue because on rare cases (15% of generations) i had this kind of json generated : {"entities": [
{"type": "Geo-Political Entity", "name": "Paris 2024"},
{"type": "Location", "name": "Paris"}],
"relations": [{"type_from": "G',
eographic Feature", "name_from": "Paris", "type_to": "Event", "name_to": "Paris 2024", "relation_type": "occurs_in"}]} |
Entering manually \r and \n isn't enough, I ended up with having another control character getting outputed as JSON, which made my json un-usable |
Updated it to exclude singlequote |
a10y
added a commit
that referenced
this issue
Apr 10, 2024
Addresses #31 Also drive-by: add support for negative `number`s
Fixed in #37 |
🖖🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, strings can for example contain a new line, not an escaped one.
Which will lead to incorrect json generation
Here is my suggestion :
I could open a PR but I could be missing something so I open an issue to discuss this
The text was updated successfully, but these errors were encountered: