Closed katrinleinweber closed 6 years ago
Ah, no, sorry! It might not be an issue in the BacDive data, but in the way R expects the escape sequences: https://github.com/jeroen/jsonlite/issues/47. I wonder whether it might be possible to detect an R client, and then deliver \\n
instead of \n
dynamically?
Fixed by cae151dd8fc448a9c8621c7df7ea06009d153579.
is a bit stupid. There should be a specific purging of invalidly escaped characters, not of all space
characters.
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 retrieve_data("Bacillus")
, which downloaded about 1.3k datasets without escaping errors.
No update to v1.0 after all, since some other kinks should be ironed out first (#68, #84, etc). v0.5
it is!
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.