You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that the bar example is quite inspiring for what we could achieve with Great Tables.
However, it would be great to have a native function like fmt_bar() to handle this directly, rather than manipulating it manually on the dataframe side.
I did a quick experiment, and the implementation seems quite straightforward:
That said, I’m also aware that introducing such a function might lead to more incoming requests for custom CSS styling around this.
So I have two thoughts on how we could approach it:
We implement a small set of fundamental functions, such as fmt_bar() and potentially a few other core utilities. More advanced or highly customized functions would be left to third-party packages (we might also need to expose fmt_by_context()). In the future, we could allow third-party functions to be mounted to GT via a register mechanism or applied through GT.pipe().
We don't include this feature directly in our project. Instead, we demonstrate the capability through documentation — for example, in the GT.fmt() section. We could rewrite the progress bar example using GT.fmt() like this:
Hello team,
I found that the bar example is quite inspiring for what we could achieve with Great Tables.
However, it would be great to have a native function like
fmt_bar()
to handle this directly, rather than manipulating it manually on the dataframe side.I did a quick experiment, and the implementation seems quite straightforward:
That said, I’m also aware that introducing such a function might lead to more incoming requests for custom CSS styling around this.
So I have two thoughts on how we could approach it:
We implement a small set of fundamental functions, such as
fmt_bar()
and potentially a few other core utilities. More advanced or highly customized functions would be left to third-party packages (we might also need to exposefmt_by_context()
). In the future, we could allow third-party functions to be mounted toGT
via aregister
mechanism or applied throughGT.pipe()
.We don't include this feature directly in our project. Instead, we demonstrate the capability through documentation — for example, in the
GT.fmt()
section. We could rewrite the progress bar example usingGT.fmt()
like this:If the team aligns with either of these options, I would be happy to contribute a PR for it!
The text was updated successfully, but these errors were encountered: