Skip to content
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

Open
wants to merge 24 commits into
base: main
Choose a base branch
from
Open

Conversation

rich-iannone
Copy link
Member

This adds the blog post for the v0.13.0 release of the package.

Copy link

codecov bot commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.86%. Comparing base (06b1408) to head (2f0f62b).

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.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 01:23 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 01:26 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 01:36 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 01:38 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 01:43 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 04:31 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 04:34 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 13:25 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 13:43 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 13:52 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 14:06 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 14:08 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 14:09 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 14:11 Destroyed
@rich-iannone rich-iannone marked this pull request as ready for review October 8, 2024 14:15
Copy link
Collaborator

@machow machow left a 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
Copy link
Collaborator

@machow machow Oct 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if instead of a list, we superimposed the loc labels onto this graph? Here's a quick example with loc.header() and friends. I crossed out the existing labels b/c I have not paint skills.

image

Copy link
Member Author

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!

docs/blog/introduction-0.13.0/index.qmd Outdated Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Outdated Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Outdated Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Outdated Show resolved Hide resolved
docs/blog/introduction-0.13.0/index.qmd Outdated Show resolved Hide resolved

gt_tbl
```

Copy link
Collaborator

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=...)`:
Copy link
Collaborator

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)

@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:38 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:39 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:39 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:41 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:42 Destroyed
@github-actions github-actions bot temporarily deployed to pr-488 October 8, 2024 21:42 Destroyed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants