* Implement reactiveConsole(). Fixes#2518
* Also includes makeReactiveBinding tweaks
* use `reactiveConsole()` to provide a nicer example
* simplified the implementation using `reactiveVal()`
* remove from documentation indexes since you probably don't want to be promoting this function
* Sassify shiny.css (& make it themable); gut json2 dependency (was there for IE8 support)
* Always serve a compressed bundle; remove shiny.css
* Use getCurrentTheme() and make sure shinyDependencies is a function
* Make sure we have sass/rprojroot before running checkBuilt.sh
* Need repos set
* Compare against bleeding edge of sass
* Perform built check with testthat (copying the approach taken for pkgdown checks)
* Update tests/testthat/test-built-files.R
Co-authored-by: Winston Chang <winston@stdout.org>
Co-authored-by: Winston Chang <winston@stdout.org>
* 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
* upgrade bootstrap-datepicker from 1.6.4 to 1.9.0; setup infrastructure for bootstraplib theming
Note also that the 000 patch is no longer relevant as 1.9.0 includes the same fix https://github.com/uxsolutions/bootstrap-datepicker/pull/2009
* Patch sass code for BS4 support and more general color contrasting
* Wrap sass compilation into reusable function
* remove check warning
* Have bootstrapPage() use bootstraplib
* yarn build
* Use new output_template()
* Deprecate bootstrapLib() in favor of bootstraplib::bootstrap()
* Require bootstraplib 0.1.0.9001
* Sync up DESCRIPTION
* document
* rollback changes to pkgdown
* Add option to use bootstraplib and have selectInput() theming variables
* Use getShinyOption()
* Have useBsTheme() error out with informative messages if a theme isn't active
* Better Sass variables defaults that account for both bootswatch themes and bs_theme_base_colors()
* Add Carson as an author
* Provide better BS3/BS4 selectize sass variable defaults as a patch to the source files
* tidy up tools script
* add sass to suggests
* yarn install && yarn build
* Wrap sass compilation into reusable function
* Bring -color-item closer to -color-input
* Leverage the new sass::output_file()
* naming change
* Sync up with other PRs
* Sync up DESCRIPTION
* Forgot to update CSS output file logic
* document
* More themable sliderInput()
* Slider's accent color default should derive from primary theme color
* Remove custom theming args (skin, accentColor, sassVars) but still support theming via bootstraplib
* Wrap sass compilation into reusable function
* remove check warning
* Make font-family configurable; auto-contrast fromto handle text color; increase color contrasting (for accessbility)
* Sync up with other PRs
* Sync up DESCRIPTION
* Forgot to update CSS output file logic
* document
* code review
