check-added-large-files (2 MB cap,
--enforce-all) and detect-private-key from
pre-commit/pre-commit-hooks (v6.0.0), and
codespell (v2.4.2) for spell-checking.
codespell runs with --write-changes and an
--ignore-words-list for domain terms (acn,
ths); renv.lock and
release_github.sh are excluded to avoid false positives on
generated content and shell identifiers.codespell, in
NEWS.md and a comment in
R/glimpse_utils.R.generate_study_config() writing unparsable YAML on
Windows. Paths were emitted as double-quoted scalars, so backslash
sequences in Windows paths (e.g. C:\Users\...) were
interpreted as YAML escapes and simulate_study() failed to
read the config. Paths are now single-quoted, which passes backslashes
through verbatim..github/workflows/pkgdown.yaml) that builds the
documentation site and deploys it to the gh-pages branch,
and set the site url in _pkgdown.yml..github/workflows/rhub.yaml) for multi-platform CRAN
checks, dispatched via rhub::rhub_check().glimpse_study() and
simulate_study_from_summary(), allowing the glimpse (which
needs the real .sas7bdat files) to run independently from
simulation.generate_study_config() (also defaulting to 123)..assert_required_id_cols() to safeguard against ID
leakage. It now errors if USUBJID/SUBJID are
present in the data but missing from id_cols, ensuring
subject IDs are regenerated synthetically rather than value-sampled from
real data.generate_study_config() to take a required
output_dir (with an optional
config_yaml_name), writing the config into that directory
alongside where synthetic data will be saved.synadam::/synadam::: syntax to
avoid the CRAN self-::: NOTE.@examples across the exported
glimpse_*/simulate_* functions. Introduce a
shared man-roxygen/setup_adam_datasets.R template that
stages bundled fixtures.LICENSE.md and switch
LICENSE to the
YEAR/COPYRIGHT HOLDER format, raise the
minimum R version to 4.1.0 (native pipe), and extend
.Rbuildignore.paramcd_filter argument.
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.