-
Notifications
You must be signed in to change notification settings - Fork 48
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
Return a tibble instead of a data.frame #415
Comments
wibeasley
added a commit
that referenced
this issue
Aug 28, 2022
wibeasley
added a commit
that referenced
this issue
Aug 30, 2022
wibeasley
added a commit
that referenced
this issue
Aug 30, 2022
wibeasley
added a commit
that referenced
this issue
Aug 30, 2022
wibeasley
added a commit
that referenced
this issue
Aug 30, 2022
wibeasley
added a commit
that referenced
this issue
Aug 30, 2022
wibeasley
added a commit
that referenced
this issue
Sep 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For a while, REDCapR functions has been using
readr::read_csv()
for a while, but has continued to (upcast to) return data.frame. There's a small chance that someone's code (that pulls a single column from a REDCap project) would break because they depend on something likeds[, 3]
returning a vector. That's the behavior of a data.frame. In contrast for tibbles,ds[, 3]
returns a single-column rectangle/tibble/data.frame.Until now, I've felt the tradeoff of (the small chance of breaking backward compatibility) favored returning a data.frame. I've changed my mind the past few weeks b/c calling
readr::problems(ds)
is informative ifds
is a tibble, but not ifds
is a data.frame.I want those parsing problems to be as easy as possible for users to determine. Returning a tibble (instead of a data.frame)
The text was updated successfully, but these errors were encountered: