-
Notifications
You must be signed in to change notification settings - Fork 214
More styling for opt_interactive()
+ new visual tests for different output formats
#1766
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
Conversation
opt_interactive()
opt_interactive()
…ames and row group labels. Part of rstudio#1693
Merge commit 'e56c3f411994fd7910f1ff428b0d74fc758ce8fe' #Conflicts: # .github/workflows/pkgdown.yaml # NEWS.md # tests/testthat/test-opt_functions.R # vignettes/case-study-gtcars.Rmd # vignettes/gt-datasets.Rmd # vignettes/gt.Rmd
Update script Update actions Update result with `source("scripts/visual-tests-latex.R")`
Let me know what you think! Here is my attempt at verifying cross-output.
There still is a bit of copy-paste needed to add more visual tests in gt-visual.qmd. I will have to think about this more. |
opt_interactive()
opt_interactive()
+ new visual tests for cross-output
I really like everything that's being done here! Visual testing is important for verifying that things are continuing to work properly so this is all much needed. |
opt_interactive()
+ new visual tests for cross-output opt_interactive()
+ new visual tests for different output formats
@olivroy I noticed this is no longer a draft PR, but, you also mentioned things left to do (but could very well be in a new PR). Given all that, is this PR ready for review / merging? |
Never mind, just saw 'ready for review' up above. Will get to that now! |
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.
LGTM!
Summary
Wonder if there is a better way to do this other than to mix and match different ihtml features.
as_gtable()
+plot.gt_tbl()
#1788 (comment)Will use this PR to make some updates as I see them fit, and will let you know once it is ready for review. I don't understand some of the code. I wonder if there is a way to do this more smoothly / automatically?
Checklist
testthat
unit tests totests/testthat
for any new functionality.