BiocCheck-class | R Documentation |
The BiocCheck
class provides a framework for reporting checks
based on Bioconductor guidelines. The class has several methods for working
with the provided checks that handle and display messages and the display
of the metadata. These methods also record the output of the BiocCheck()
report in both plain text and JSON formats.
Note that currently, multiple BiocCheck
runs will interfere with
each other given that they are implemented via a reference class semantic.
When running multiple checks in the same session, you can separate these
instances by running them in separate processes (e.g., via BiocParallel
).
The metadata includes a number of standard fields to allow easier troubleshooting and display of potentially relevant information. Currently, the fields included are
The version of the BiocCheck package
The version of Bioconductor
The name of the package in check
The version of the package in check
The directory of the package source or tarball in check
The directory where the package is installed for testing, a temporary location by default
The directory where the <package>.BiocCheck
folder
is saved. Usually the same folder as the package in check
The platform/OS where the check is taking place
Whether the package in check is a source directory or a tarball
A BiocCheck
instance
log
list()
A running list of all conditions raised (i.e., notes,
warnings, errors)
check
character(1)
The title of the last check used for logging
purposes.
error,
warning, note list()
Finer extraction of each condition type
metadata
list()
A list of additional information relevant to the
package and its state. See details.
verbose
logical(1)
Whether to show the full information pertaining
to the checks. A FALSE
value will only show the condition messages
and not any relevant files or additional information. The defaults are
FALSE
and TRUE
for BiocCheck
and BiocCheckGitClone
, respectively.
Message-class
bc <- BiocCheck:::.BiocCheck
bc$verbose
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.