CRAN Package Check Results for Package shinyalert

Last updated on 2023-11-27 19:52:54 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.0.0 1.89 21.36 23.25 NOTE
r-devel-linux-x86_64-debian-gcc 3.0.0 1.83 17.91 19.74 NOTE
r-devel-linux-x86_64-fedora-clang 3.0.0 30.56 NOTE
r-devel-linux-x86_64-fedora-gcc 3.0.0 28.25 NOTE
r-devel-windows-x86_64 3.0.0 3.00 42.00 45.00 OK
r-patched-linux-x86_64 3.0.0 2.07 21.47 23.54 OK
r-release-linux-x86_64 3.0.0 2.14 20.92 23.06 OK
r-release-macos-arm64 3.0.0 17.00 OK
r-release-macos-x86_64 3.0.0 20.00 OK
r-release-windows-x86_64 3.0.0 4.00 40.00 44.00 OK
r-oldrel-macos-arm64 3.0.0 16.00 NOTE
r-oldrel-macos-x86_64 3.0.0 26.00 NOTE
r-oldrel-windows-x86_64 3.0.0 6.00 47.00 53.00 OK

Check Details

Version: 3.0.0
Check: Rd files
Result: NOTE checkRd: (-1) shinyalert.Rd:159: Lost braces; missing escapes or markup? 159 | Modals created with {shinyalert} have a return value when they exit. | ^ checkRd: (-1) shinyalert.Rd:180: Lost braces; missing escapes or markup? 180 | For example, using the following {shinyalert} code will result in a modal with | ^ checkRd: (-1) useShinyalert.Rd:21: Lost braces; missing escapes or markup? 21 | The first time a {shinyalert} message is shown, the required scripts are | ^ checkRd: (-1) useShinyalert.Rd:12: Lost braces; missing escapes or markup? 12 | \item{force}{Set to \code{TRUE} to force pre-loading the {shinyalert} scripts. If | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 3.0.0
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘stats’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-oldrel-macos-arm64, r-oldrel-macos-x86_64