-
Notifications
You must be signed in to change notification settings - Fork 46
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
"Error: 'levels.drive_id()' not supported." when using apply on drive_ls() output #369
Comments
I believe you've come across another variation of this issue: r-lib/vctrs#1416. It turns out base R, in some of the apply functions, calls I'm not convinced adding a My preferred solution is to use functions within the tidyverse to work with such a vector, e.g. to use I think your choices, certainly near-term, are to either switch to something like |
Note to self: Update on where this went in vctrs: r-lib/vctrs#1186 |
vctrs has since made a change that prevents this weird error about |
Thank you very much for this great project.
When using
apply
on the output ofdrive_ls()
withgoogledrive
2.0.0
from CRAN or this repo (e.g. to row-by-row create sub-folders and download the respective files) the errorError: 'levels.drive_id()' not supported.
is thrown. With version1.0.1
, it is possible to runapply
on the output ofdrive_ls()
without this error and without converting IDs to character.See the reprex below orientated on the workflow that I have been using:
Calling
download_files()
withgoogledrive
2.0.0
fails:Calling
apply
on adrive_ls()
output works withgoogledrive
1.0.1
or by converting the IDs to character and removing thedrive_resource
column:Created on 2021-07-26 by the reprex package (v2.0.0)
Could it be that there is a method missing for class
"drive_id" "vctrs_vctr" "character"
?Its not so problematic for me since I simply can convert to character but maybe it would be convenient if
apply
would work directly.Thanks!
sessionInfo
EDIT: reprex with the remote examples
The text was updated successfully, but these errors were encountered: