-
Notifications
You must be signed in to change notification settings - Fork 80
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
Printing more rows than default max has unexpected behavior #734
Comments
Thanks for this report. Can you clarify what you mean by printing "the same thing"?
sum_cut has 5 rows while sum_cut_color is 35 rows. So you wouldn't expect them to be identical when they print because they are not identical objects. Can you clarify what you mean by expecting them to print the same thing? |
One prints as a nice html table and one does not. The n parameter on print also seems to be ignored |
I think it's the use of the print() function I don't see how they should be impacted by the value of n. When I use n=3 I get 3 rows so I think the parameter is not ignored. However it does seem like knit_print.skim_one_df() is not being used. However, using https://rpubs.com/elinw/1024699 @michaelquinn32 It seems like something is going wrong with the print dispatch? Or is calling print explicitly essentially an override? |
I did notice that things seemed to go a bit wild with several hundred variables all of the same type. Maybe we need to be thinking about pagination. |
If I have a summary which is long, I sometimes want to add
print(n=bignumber)
to the end to get all of the summary to print but this doesn't behave as I would expect. Below, I would expect Example 1 and Example 2 to print the same thing but they don't. This is more important when I have even more rows as is true in example 3 and 4. It seems n is being ignored altogetherHere's a reprex to show:
Variable type: numeric
Variable type: numeric
Created on 2023-04-03 with reprex v2.0.2
Session info
The text was updated successfully, but these errors were encountered: