* Get rid of the bootstraplib option and simply use bootstraplib when a theme is active
* Restore previous bootstraplib theme when exiting a file/dir based runApp
* wip use latest htmltools+bootstraplib to sketch out local theme API
* Don't do anything with bootstraplib's global state and make sure bs_theme is an expected value
* typo
* better docs
* bugfix
* Use the new, more general, tagFunction() instead
* Set the theme object as a part of the page layout (instead of in shinyApp())
* rollback the structural changes to selectizeIt() to avoid breaking code that makes assumptions about the return value of selectInput()
* set shinyOption() in bootstrapLib(), not bootstrapPage()
* Add a helper for checking whether theme is a bs_theme
* Make theme a required arg in bootstrapSass
* Have bootstrapLib() call shinyOption() at render-time, and document why it works
* Have bootstrapPage() always place bootstrapLib(theme) at the top of the tagList()
* Only set shinyOption() when an application is running at render-time (otherwise; throw a warning)
* code review
* Export a new getCurrentTheme() for Shiny developers to access the theme's Sass code
* bump version
Enables markdown. Only observed one non-whitespace difference on a line
that had used backticks previously which were previously not being
parsed as a code block.
-explicitly using the `title` parameter of the top-level page function.
+explicitly using the \code{title} parameter of the top-level page function.
These functions were temporarily ripped out of Shiny and moved
to the htmltools package. We've discovered that it's safe to
keep including them in shiny; as long as the functions in shiny
and the functions in htmltools are identical, the user won't
receive a conflict warning.
- Combine sliderInput and animationOptions topics
- Provide better staticdoc index descriptions
Sorry for the big diff, that's due to using a newer version of roxygen.
