-
Notifications
You must be signed in to change notification settings - Fork 61
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
blog: add the v0.13.0 release post #488
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #488 +/- ##
=======================================
Coverage 87.86% 87.86%
=======================================
Files 42 42
Lines 4852 4852
=======================================
Hits 4263 4263
Misses 589 589 ☔ View full report in Codecov by Sentry. |
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.
This is looking great, and the example legit helped me wrap my head around all the loc specifiers!
The lead-in to examples feels like it might be a bit too long, and do a lot of factual and procedural breakdowns / enumeration beforehand. I left suggestions to cut down and move some of this to after examples. Feel free to use, tweak, and punt to your heart's delight! (I'm okay with us posting any version of this including as is)
|
||
In `v0.13.0`, we can target much more than just the table body! Here is the expanded set of `loc.*()` methods along with the locations that they can target. | ||
|
||
- `loc.title()`: the table title |
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.
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.
Excellent idea and much more direct. I will work on this and get it in soon!
|
||
gt_tbl | ||
``` | ||
|
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.
Could note that column_header()
targets both loc.column_labels() and loc.spanner_labels(), and then link to composite selector page etc...
|
||
### How `tab_style()` fits in with `tab_options()` | ||
|
||
When it comes to styling, you can use `tab_options()` for some of the basics and use `tab_style()` for the more demanding styling tasks. And you could combine the usage of both in your table. The precedence (or priority) is given to `tab_style()`, regardless of the order of invocation. As an example of this, we can add a background color to all remaining locations with `tab_options(table_background_color=...)`: |
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.
I would move this to after the example, with a short sentence explaining to people what is changing in the table (e.g. HoneyDew fill)
Co-authored-by: Michael Chow <[email protected]>
Co-authored-by: Michael Chow <[email protected]>
Co-authored-by: Michael Chow <[email protected]>
Co-authored-by: Michael Chow <[email protected]>
Co-authored-by: Michael Chow <[email protected]>
This adds the blog post for the v0.13.0 release of the package.