-
Notifications
You must be signed in to change notification settings - Fork 12
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
Remove invalid \n in JSON #43
Comments
Ah, no, sorry! It might not be an issue in the BacDive data, but in the way R expects the escape sequences: jeroen/jsonlite#47. I wonder whether it might be possible to detect an R client, and then deliver |
Fixed by cae151d. |
Lines 94 to 99 in cae151d
is a bit stupid. There should be a specific purging of invalidly escaped characters, not of all |
Since this changes the output datasets, it might as well be the reason to bump the semantic version to 1.0. #14 also supports this. |
tested with |
While implementing #31 and switching from
rjson
tojsonlite
I noticed that some fields contain a insufficiently escaped\n
s. This results inlexical error: invalid character inside string.
.@ceb15: Please consider ensuring that those are escaped as
\\n
already BacDive or (I presume) during JSON serialisation.I'll parse them away for now.
The text was updated successfully, but these errors were encountered: