* using log directory 'd:/RCompile/CRANincoming/R-devel/flowchart.Rcheck' * using R Under development (unstable) (2024-01-31 r85845 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 12.3.0 GNU Fortran (GCC) 12.3.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'flowchart/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'flowchart' version '0.1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'Pau Satorra ' New submission Possibly misspelled words in DESCRIPTION: dataframe (12:91, 12:403) generalisability (12:245) tidyverse (12:107) The Description field should not start with the package name, 'This package' or similar. * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'flowchart' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking 'build' directory ... 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 loading without being on the library search path ... OK * checking use of S3 registration ... 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 ... NOTE checkRd: (-1) as_fc.Rd:24: Lost braces; missing escapes or markup? 24 | \item{text_pattern}{Structure that will have the text in the box. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n{N}".} | ^ checkRd: (-1) as_fc.Rd:24: Lost braces 24 | \item{text_pattern}{Structure that will have the text in the box. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n{N}".} | ^ checkRd: (-1) fc_filter.Rd:36: Lost braces; missing escapes or markup? 36 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_filter.Rd:36: Lost braces; missing escapes or markup? 36 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_filter.Rd:36: Lost braces; missing escapes or markup? 36 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_filter.Rd:44: Lost braces; missing escapes or markup? 44 | \item{text_pattern_exc}{Structure that will have the text in each of the excluded boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_filter.Rd:44: Lost braces; missing escapes or markup? 44 | \item{text_pattern_exc}{Structure that will have the text in each of the excluded boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_filter.Rd:44: Lost braces; missing escapes or markup? 44 | \item{text_pattern_exc}{Structure that will have the text in each of the excluded boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_split.Rd:28: Lost braces; missing escapes or markup? 28 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_split.Rd:28: Lost braces; missing escapes or markup? 28 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ checkRd: (-1) fc_split.Rd:28: Lost braces; missing escapes or markup? 28 | \item{text_pattern}{Structure that will have the text in each of the boxes. It recognizes label, n, N and perc within brackets. For default it is "{label}\\n {n} ({perc}\%)".} | ^ * 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 ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking contents of 'data' directory ... OK * checking data for non-ASCII characters ... OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking installed files from 'inst/doc' ... OK * checking files in 'vignettes' ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... OK * checking PDF version of manual ... [21s] OK * checking HTML version of manual ... OK * DONE Status: 2 NOTEs