We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thanks for the package!
This is a more general question about the data.frame requirement of the output of rio::import.
This makes it so that some rds files (which could contain anything) don't import. For example, I have a stanfit (https://cran.r-project.org/web/packages/rstan/vignettes/stanfit-objects.html) object stored in an RDS.
Is accessing other types of R objects in an RDS out-of-scope for rio::import?
The text was updated successfully, but these errors were encountered:
Generally yes, but we should probably make an exception for RDS and Rdata files, given they can contain arbitrary R objects.
Sorry, something went wrong.
This is now implemented.
allow import/export of non-DFs from rds, rdata (closes #183)
43d544b
data.table
setclass
No branches or pull requests
Thanks for the package!
This is a more general question about the data.frame requirement of the output of rio::import.
This makes it so that some rds files (which could contain anything) don't import. For example, I have a stanfit (https://cran.r-project.org/web/packages/rstan/vignettes/stanfit-objects.html) object stored in an RDS.
Is accessing other types of R objects in an RDS out-of-scope for rio::import?
The text was updated successfully, but these errors were encountered: