The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Utilizing the 'logger' framework to record events within a package, specific to 'teal' family of packages. Supports logging namespaces, hierarchical logging, various log destinations, vectorization, and more.
Version: | 0.3.0 |
Depends: | R (≥ 3.6) |
Imports: | glue (≥ 1.0.0), lifecycle (≥ 0.2.0), logger (≥ 0.3.0), methods, shiny (≥ 1.6.0), utils, withr (≥ 2.1.0) |
Suggests: | knitr (≥ 1.42), rmarkdown (≥ 2.23), testthat (≥ 3.1.7) |
Published: | 2024-10-24 |
DOI: | 10.32614/CRAN.package.teal.logger |
Author: | Dawid Kaledkowski [aut, cre], Konrad Pagacz [aut], F. Hoffmann-La Roche AG [cph, fnd] |
Maintainer: | Dawid Kaledkowski <dawid.kaledkowski at roche.com> |
BugReports: | https://github.com/insightsengineering/teal.logger/issues |
License: | Apache License 2.0 |
URL: | https://insightsengineering.github.io/teal.logger/, https://github.com/insightsengineering/teal.logger/ |
NeedsCompilation: | no |
Language: | en-US |
Materials: | README NEWS |
CRAN checks: | teal.logger results |
Reference manual: | teal.logger.pdf |
Vignettes: |
Getting started (source) |
Package source: | teal.logger_0.3.0.tar.gz |
Windows binaries: | r-devel: teal.logger_0.3.0.zip, r-release: teal.logger_0.3.0.zip, r-oldrel: teal.logger_0.3.0.zip |
macOS binaries: | r-release (arm64): teal.logger_0.3.0.tgz, r-oldrel (arm64): teal.logger_0.3.0.tgz, r-release (x86_64): teal.logger_0.3.0.tgz, r-oldrel (x86_64): teal.logger_0.3.0.tgz |
Old sources: | teal.logger archive |
Reverse imports: | teal, teal.modules.clinical, teal.modules.general, teal.slice, teal.transform |
Please use the canonical form https://CRAN.R-project.org/package=teal.logger to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.