-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: improve as_duckplyr_df()
error message for invalid .data
#339
Conversation
This is how benchmark results would change (along with a 95% confidence interval in relative change) if cf2b613 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I'm just envisioning someone removing that seemingly extra space in a future revision.
tests/testthat/test-as_duckplyr_df.R
Outdated
|
||
by_cyl <- dplyr::group_by(mtcars, cyl) | ||
expect_snapshot(error = TRUE, { | ||
as_duckplyr_df(by_cyl) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe in this case the error is misleading, would you convert a grouped data.frame by converting it thus losing its grouping
This is how benchmark results would change (along with a 95% confidence interval in relative change) if e718a07 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
Thanks! |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if c6e74b8 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
as_duckplyr_df()
error message for invalid .data
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 62158a5 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if cc277ed is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
For #127
Not docs but this was a low-hanging fruit to warm up. 😉