tweaks to unark for more robust parsing #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
unark()
will strip out non-compliant characters by default.unark()
is also be more flexible, allowing the user to specify the corresponding table names manually, rather than enforcing they correspond with the incoming csv names. #18Technical tweak: readLines call inside
unark()
method will use encoding directly fromgetOption("encoding")
, e.g. allowing encoding to be set to UTF-8.This can resolve parsing errors when using the readr parser on certain files. See
FAO.R
example inexamples
for an illustration.cc @noamross thanks for reporting these issues and maybe for testing this out too.