Chang W, Cheng J, Allaire J, Sievert C, Schloerke B, Xie Y, Allen J, McPherson J, Dipert A, Borges B (2024). shiny: Web Application Framework for R. -R package version 1.8.1.9001, +R package version 1.9.0, https://github.com/rstudio/shiny, https://shiny.posit.co/.
@Manual{,
title = {shiny: Web Application Framework for R},
author = {Winston Chang and Joe Cheng and JJ Allaire and Carson Sievert and Barret Schloerke and Yihui Xie and Jeff Allen and Jonathan McPherson and Alan Dipert and Barbara Borges},
year = {2024},
- note = {R package version 1.8.1.9001,
+ note = {R package version 1.9.0,
https://github.com/rstudio/shiny},
url = {https://shiny.posit.co/},
}
diff --git a/index.html b/index.html
index e614e4c4e..0a11d129c 100644
--- a/index.html
+++ b/index.html
@@ -34,7 +34,7 @@
diff --git a/news/index.html b/news/index.html
index f19c18fb0..b4a2e6bf3 100644
--- a/news/index.html
+++ b/news/index.html
@@ -17,7 +17,7 @@
@@ -44,18 +44,18 @@
Shiny now includes busy indication by default, which more specifically means: 1. Calculating/recalculating outputs now have a spinner overlay. 2. When no outputs are calculating, but Shiny is busy calculating something (e.g., a download, side-effect, etc), a page-level pulsing banner is shown.
If either 1 or 2 leads to undesirable behavior in your app, you can disable them entirely with useBusyIndicators(spinners = FALSE, pulse = FALSE). In addition, various properties of the spinners and pulse can be customized with busyIndicatorOptions(). For more details, see ?busyIndicatorOptions. (#4040, #4104)
The client-side TypeScript code for Shiny has been refactored so that the Shiny object is now an instance of class ShinyClass. (#4063)
In TypeScript, the Shiny object has a new property initializedPromise, which is a Promise-like object that can be awaited or chained with .then(). This Promise-like object corresponds to the shiny:sessioninitialized JavaScript event, but is easier to use because it can be used both before and after the events have occurred. (#4063)
Output bindings now include the .recalculating CSS class when they are first bound, up until the first render. This makes it possible/easier to show progress indication when the output is calculating for the first time. (#4039)
Added function reactlogAddMark() to programmatically add _mark_ed locations in the reactlog log without the requirement of keyboard bindings during an idle reactive moment. (#4103)
downloadButton() and downloadLink() are now disabled up until they are fully initialized. This prevents the user from clicking the button/link before the download is ready. (#4041)
Output bindings that are removed, invalidated, then inserted again (while invalidated) now correctly include the .recalculating CSS class. (#4039)
Fixed a recent issue with uiOutput() and conditionalPanel() not properly lower opacity when recalculation (in a Bootstrap 5 context). (#4027)
Added ExtendedTask, a new simple way to launch long-running asynchronous tasks that are truly non-blocking. That is, even within a session, an ExtendedTask won’t block the main thread from flushing the reactive graph (i.e., UI updates won’t be blocked). ExtendedTask pairs nicely with new bslib::input_task_button() and bslib::bind_task_button() functions, which help give user feedback and prevent extra button clicks. (#3958)
Added ExtendedTask, a new simple way to launch long-running asynchronous tasks that are truly non-blocking. That is, even within a session, an ExtendedTask won’t block the main thread from flushing the reactive graph (i.e., UI updates won’t be blocked). ExtendedTask pairs nicely with new bslib::input_task_button() and bslib::bind_task_button() functions, which help give user feedback and prevent extra button clicks. (#3958)
Added a JavaScript error dialog, reporting errors that previously were only discoverable by opening the browser’s devtools open. Since this dialog is mainly useful for debugging and development, it must be enabled with shiny::devmode(). (#3931)
runExample() now uses the bslib package to generate a better looking result. It also gains a package argument so that other packages can leverage this same function to run Shiny app examples. For more, see ?runExample. (#3963, #4005)
Added onUnhandledError() to register a function that will be called when an unhandled error occurs in a Shiny app. Note that this handler doesn’t stop the error or prevent the session from closing, but it can be used to log the error or to clean up session-specific resources. (thanks @JohnCoene, #3993)
Bootstrap 5 support. (#3410 and rstudio/bslib#304)
bslib::bs_theme(version = 5) to a page layout function with a theme argument (e.g., fluidPage(), navbarPage(), etc).Closed #3322, #3313, #1823, #3321, #3320, #1928, and #2310: Various improvements to navbarPage(), tabsetPanel(), tabPanel(), navbarMenu(), etc. Also, these functions are now powered by the bslib package’s new nav() API (consider using bslib’s API to create better looking and more fully featured navs). (#3388)
Closed #3322, #3313, #1823, #3321, #3320, #1928, and #2310: Various improvements to navbarPage(), tabsetPanel(), tabPanel(), navbarMenu(), etc. Also, these functions are now powered by the bslib package’s new nav() API (consider using bslib’s API to create better looking and more fully featured navs). (#3388)
All uses of list(...) have been replaced with rlang::list2(...). This means that you can use trailing , without error and use rlang’s !!! operator to “splice” a list of argument values into .... We think this’ll be particularly useful for passing a list of tabPanel() to their consumers (i.e., tabsetPanel(), navbarPage(), etc). For example, tabs <- list(tabPanel("A", "a"), tabPanel("B", "b")); navbarPage(!!!tabs). (#3315 and #3328)
installExprFunction() and exprToFunction() are now able to handle quosures when quoted = TRUE. So render-functions which call these functions (such as with htmlwidgets) can now understand quosures. Users can also use rlang::inject() to unquote a quosure for evaluation. This also means that render function no longer need env and quoted parameters; that information can be embedded into a quosure which is then passed to the render function. Better documentation was added for how to create render functions. (#3472)
icon(lib="fontawesome") is now powered by the fontawesome package, which will make it easier to use the latest FA icons in the future (by updating the fontawesome package). (#3302)
This release focuses on improvements in three main areas:
theme argument of fluidPage(), navbarPage(), and bootstrapPage() all now understand bslib::bs_theme() objects, which can be used to opt-into Bootstrap 4, use any Bootswatch theme, and/or implement custom themes without writing any CSS.session object now includes $setCurrentTheme() and $getCurrentTheme() methods to dynamically update (or obtain) the page’s theme after initial load, which is useful for things such as adding a dark mode switch to an app or some other “real-time” theming tool like bslib::bs_themer().theme argument of fluidPage(), navbarPage(), and bootstrapPage() all now understand bslib::bs_theme() objects, which can be used to opt-into Bootstrap 4, use any Bootswatch theme, and/or implement custom themes without writing any CSS.session object now includes $setCurrentTheme() and $getCurrentTheme() methods to dynamically update (or obtain) the page’s theme after initial load, which is useful for things such as adding a dark mode switch to an app or some other “real-time” theming tool like bslib::bs_themer().{bslib}’s website
reactive() and render*() (e.g. renderText(), renderTable(), etc) expressions.R/extended-task.R
+ Source: R/extended-task.R
ExtendedTask.Rd