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
Running reactR::scaffoldReactWidget() on an otherwise R CMD check-passing boilerplate package repo, even before running system("yarn install"); system("yarn run webpack") creates a warning (see full log below).
It's not super important, but I think it might remove some friction if setting up the scaffolding kept the package intact warning-free.
You can see the changes I needed to make to the boilerplate to pass devtools::check()in this commit
Comes down to a couple of @inheritParams and friends.
If you agree with this kind of change, I'd be happy to see whether I can work this in a PR.
==> devtools::check()
Updating reacthexgrid documentation
Warning: @param [/Users/max/GitHub/reacthexgrid/R/reacthexgrid.R#31]: mismatched braces or quotes
Writing NAMESPACE
Loading reacthexgrid
Writing NAMESPACE
── Building ──────────── reacthexgrid ──
Setting env vars:
● CFLAGS : -Wall -pedantic -fdiagnostics-color=always
● CXXFLAGS : -Wall -pedantic -fdiagnostics-color=always
● CXX11FLAGS: -Wall -pedantic -fdiagnostics-color=always
────────────────────────────────────────
✔ checking for file ‘/Users/max/GitHub/reacthexgrid/DESCRIPTION’ ...
─ preparing ‘reacthexgrid’:
✔ checking DESCRIPTION meta-information ...
─ checking for LF line-endings in source and make files and shell scripts
─ checking for empty or unneeded directories
─ building ‘reacthexgrid_0.0.0.9000.tar.gz’
── Checking ──────────── reacthexgrid ──
Setting env vars:
● _R_CHECK_CRAN_INCOMING_USE_ASPELL_: TRUE
● _R_CHECK_CRAN_INCOMING_REMOTE_ : FALSE
● _R_CHECK_CRAN_INCOMING_ : FALSE
● _R_CHECK_FORCE_SUGGESTS_ : FALSE
── R CMD check ─────────────────────────────────────────────────────────────────
* using log directory ‘/Users/max/GitHub/reacthexgrid.Rcheck’
* using R version 3.6.1 (2019-07-05)
* using platform: x86_64-apple-darwin15.6.0 (64-bit)
* using session charset: UTF-8
* using options ‘--no-manual --as-cran’
* checking for file ‘reacthexgrid/DESCRIPTION’ ... OK
* this is package ‘reacthexgrid’ version ‘0.0.0.9000’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking serialization versions ... OK
* checking whether package ‘reacthexgrid’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... WARNING
Undocumented arguments in documentation object 'reacthexgrid-shiny'
‘width’ ‘height’ ‘id’ ‘style’ ‘class’ ‘...’
Undocumented arguments in documentation object 'reacthexgrid'
‘message’ ‘width’ ‘height’ ‘elementId’
Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... NONE
* DONE
Status: 1 WARNING
See
‘/Users/max/GitHub/reacthexgrid.Rcheck/00check.log’
for details.
── R CMD check results ──────────────────────────── reacthexgrid 0.0.0.9000 ────
Duration: 12.6s
❯ checking Rd \usage sections ... WARNING
Undocumented arguments in documentation object 'reacthexgrid-shiny'
‘width’ ‘height’ ‘id’ ‘style’ ‘class’ ‘...’
Undocumented arguments in documentation object 'reacthexgrid'
‘message’ ‘width’ ‘height’ ‘elementId’
Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
0 errors ✔ | 1 warning ✖ | 0 notes ✔
Error: R CMD check found WARNINGs
Execution halted
Exited with status 1.
note to self: the above commit borks up the html root element; 5bb34a657e5a9dbd50658cc0ff469dcb0691ae2b fixes it and the warnings from devtools::check(), so this should be the base for my PR.
Running
reactR::scaffoldReactWidget()
on an otherwiseR CMD check
-passing boilerplate package repo, even before runningsystem("yarn install"); system("yarn run webpack")
creates a warning (see full log below).It's not super important, but I think it might remove some friction if setting up the scaffolding kept the package intact warning-free.
You can see the changes I needed to make to the boilerplate to pass
devtools::check()
in this commitComes down to a couple of
@inheritParams
and friends.If you agree with this kind of change, I'd be happy to see whether I can work this in a PR.
The text was updated successfully, but these errors were encountered: