You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with this approach is that the may.app object is created when the package is built (or installed) rather than when the user actually calls may.app. This can lead to subtle bugs when your package is installed or built with an older version of shiny and then the user later updates their version of shiny.
It's also problematic because warnings emitted by any of the shiny functions you've used become installation errors. We are in the process of deprecating shiny::dataTableOutput() in favor of functions provided by the DT package, and we will soon be emitting a warning when dataTableOutput() is called to inform users of this change. Because may.app is created at buildtime rather than runtime, the warning shows up when the package is installed, rather than when the user starts the app.
To fix this, please convert may.app and other app objects into functions:
We are working on releasing shiny 1.8.1 now that informs users of the deprecation using message(). We plant to start to emit warnings in the following version of shiny.
The text was updated successfully, but these errors were encountered:
There appear to be several Shiny apps in this package that are built in this way
epimdr2/source/R/shiny2.r
Lines 13 to 16 in c359ca0
The problem with this approach is that the
may.app
object is created when the package is built (or installed) rather than when the user actually callsmay.app
. This can lead to subtle bugs when your package is installed or built with an older version of shiny and then the user later updates their version of shiny.It's also problematic because warnings emitted by any of the shiny functions you've used become installation errors. We are in the process of deprecating
shiny::dataTableOutput()
in favor of functions provided by the DT package, and we will soon be emitting a warning whendataTableOutput()
is called to inform users of this change. Becausemay.app
is created at buildtime rather than runtime, the warning shows up when the package is installed, rather than when the user starts the app.To fix this, please convert
may.app
and other app objects into functions:We are working on releasing shiny 1.8.1 now that informs users of the deprecation using
message()
. We plant to start to emit warnings in the following version of shiny.The text was updated successfully, but these errors were encountered: