-
Notifications
You must be signed in to change notification settings - Fork 79
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
group_by not always working #736
Comments
I don't think the issue is the number of rows. It's with the classes. Is it possible to isolate which data type is causing the problem by filtering prior to skimming? |
Hi @elinw So now I can generate a reprex: This seems like a bug to me? |
For sure a bug. Thanks for the report! |
@michaelquinn32 When all values are NA and |
Okay I take it back, because there is no such thing as
So then the pipe ends up passing nothing along to the final steps. Update:
I guess the question is, do we want to silence the warnings? Or would we want to handle like a numeric since I don't think min and max are defined for the date class. Consistency with Numeric would return NA for both min and max. |
@elinw |
For some data frames I get an error when applying group_by before skim(). Doesn’t seem to depend on the grouping variable type.
![image](https://user-images.githubusercontent.com/96417363/234005003-b831f753-6eb3-4481-867a-061e4d5acc87.jpg)
this issue doesn’t come up for iris though where it works.
I’m not sure how to provide a reprex for this. Is this a known issue? Any way to resolve it?
The text was updated successfully, but these errors were encountered: