Closed donyunardi closed 1 year ago
Hi @kumamiao
Currently, as you browse with bslib::run_with_themer
, you get an output like this:
#### Update your bs_theme() R code with: #####
bs_theme_update(theme, bootswatch = "lux")
I think the idea is that you would copy bootswatch = "lux"
and add it to the current bs_theme
argument in your options
statement.
options("teal.bs_theme" = bslib::bs_theme(version = "5", bootswatch = "lux"))
We don't really use bs_theme_update
independently, outside of bslib::run_with_themer
.
Is this what your question is about?
If so, perhaps we need to provide detail instruction on which one to copy from run_with_themer
output during exploring in the vignette?
Or, maybe I misunderstood the question?
We don't really use bs_theme_update independently, outside of bslib::run_with_themer.
Is this what your question is about? If so, perhaps we need to provide detail instruction on which one to copy from run_with_themer output during exploring in the vignette?
Yes exactly. In this part of the vignette we actually did provide both ways of running the options (bslib::bs_theme_update()
in addition to bslib:: bs_theme()
).
After user gets the bs_theme_update(...)
output after exploring different themes and color changes, the natural thing to do might be to plug it directly - we could either showcase both options as examples, or provide detailed instruction on plugging in the results into bslib:: bs_theme()
if that's recommended instead.
As a separate request within this task - please include some figures / screen-shots.
run_with_themer
and applying the desired changes using bs_theme_update
.
_Originally posted by @kumamiao in https://github.com/insightsengineering/teal/pull/727#discussion_r981686873_