rio
rio copied to clipboard
gesistsa
🐟 A Swiss-Army Knife for Data I/O
Or else updating both the readme and the vignette would be a chore.
As you might notice, [leeper/rio](https://github.com/leeper/rio) got redirected to here. That's because Thomas transferred the repo as well as the maintainership of `rio` to me. I am now the maintainer of...
https://github.com/gesistsa/rio/blob/81c04236dab444aaea9b9ca953f48ccc33ba4d88/tests/testthat/test_compress.R#L3-L27 https://github.com/gesistsa/rio/blob/81c04236dab444aaea9b9ca953f48ccc33ba4d88/R/compression.R#L18 It only tests `zip` and `tar`. `gzip` (implemented in #123 ) is untested. https://github.com/gesistsa/rio/blob/81c04236dab444aaea9b9ca953f48ccc33ba4d88/R/import.R#L112-L116 So do formats such as `xz` and `bzip2`.
`ledger` by @trevorld has support for `rio`, even though it is not in `rio`'s `Suggests`. And of course, the code is not in this package. Currently, `rio` raises error with...
(We can ignore the long line) ``` ── GP rio ────────────────────────────────────────────────────────────────────── It is good practice to ✖ write unit tests for all functions, and all package code in general. 84%...
[CVE-2024-27322](https://nvd.nist.gov/vuln/detail/CVE-2024-27322) is partially fixed in R 4.4.0. But the attack surface is still there. First, this package supports R > 3.6 therefore the partial fix in 4.4.0 is not applied...
``` r ## fwrite can do this automatically, so this is a special case R.utils::isGzipped(rio::export(iris, tempfile(fileext = ".csv.gz")), method = "content") #> [1] TRUE ## But not this R.utils::isGzipped(rio::export(iris, tempfile(fileext...
As there are many bugs (#395 #396 #399) after really testing this bunch of code (#354) Other than the issues of compression detection, this https://github.com/gesistsa/rio/blob/2fb1373a497f586dacce095300452ccc5a42cf37/R/compression.R#L25-L44 is super not robust (e.g....
https://github.com/gesistsa/rio/blob/2fb1373a497f586dacce095300452ccc5a42cf37/R/import.R#L44 It also circles back to #313