feat: Add fmt_image_circle() and vals.fmt_image_circle() functions#676
feat: Add fmt_image_circle() and vals.fmt_image_circle() functions#676jrycw wants to merge 1 commit into
fmt_image_circle() and vals.fmt_image_circle() functions#676Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #676 +/- ##
==========================================
+ Coverage 91.17% 91.21% +0.03%
==========================================
Files 47 47
Lines 5462 5495 +33
==========================================
+ Hits 4980 5012 +32
- Misses 482 483 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@jrycw would you be able to resubmit this feature/PR to posit-dev/gt-extras? |
@rich-iannone, that's a great suggestion. I think we can close this PR now. Would you be able to port the code over or create an issue there? My laptop has been down for a few days, so I'd appreciate the help. |
I can do that! |
|
I am closing this PR because posit-dev/gt-extras#164 has been merged. |
Hello team,
This PR addresses #354.
Rather than modifying the existing
fmt_image()to accommodate border-related parameters, I have renamed the currentfmt_image()to_fmt_image(), and introduced newfmt_image()andfmt_image_circle()functions as thin wrappers around it. Keeping_fmt_image()andFmtImageunder our control gives us greater flexibility to add more parameters in the future if needed.Here’s a short demo to illustrate the usage:
One thing that seems odd to me is that
NotImplementedErrordoesn’t appear to be raised as expected during execution, yet our tests still pass.For instance, when running the following code, I would expect it to break, but instead, the print statement after
vals.fmt_image()is executed successfully, which feels strange.