-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't statically copy shiny::tabPanel
and shiny::renderUI
at build time
#151
Conversation
shiny::tabPanel
at build timeshiny::tabPanel
and shiny::renderUI
at build time
Thanks @wch. I'll merge today and re-submit. |
@wch : I have to align |
Thank you for the quick response! |
shinydashboardPlus, shinyMobile and bs4Dash are all updated and on CRAN. Dear maintainer, thanks, package bs4Dash_2.0.3.tar.gz is on its way to CRAN. Best regards, Afficher le message d’origine No changes to worse in reverse depends. |
Was this done? |
I have rolled back to |
Maybe somenthing else is missing. I have to re-check. |
Something unclear: is your app using bs4Dash and shinydashboardPlus at the same time? From you log I can't say. |
I can reproduce this (using the latest CRAN versions) with the
results in:
However, I'm not sure if this is still Edit: No, this seems to be a |
Good catch! Thx |
@DivadNojnarg : I am not explicitly using bs4Dash just updated the package (thinking there may be a dependency). |
Please update when this is fixed... in the meantime, are there any workarounds? |
As reported above, it's not a |
With the upcoming Shiny 1.7.0 release candidate, the old previous code caused the following error in
R CMD check
:This is because the following line copies the function directly from the installed version of Shiny, and in Shiny 1.7.0, that function contains a call to
bslib::nav()
:There are additional reasons that it is dangerous to copy objects from another package at build time, which is what that line does. It means that the object will be copied from the version of Shiny installed when shinydashboardPlus was built, but if the version of Shiny is later update, then shinydashboardPlus will still have the old version of the function copied from the old version of Shiny.
Please read https://r-pkgs.org/r.html#aliasing-a-function for more information about possible problems from copying functions at package build time.
If you could please merge and release a new version as soon as possible, we would appreciate it, as this is a blocker for the upcoming Shiny 1.7.0.