LoginSign Up
← Back to all sparks
L

logrx

ANALYTICS
Velocity0.0

Tools to facilitate logging in a clinical environment with the goal of making code easily traceable and reproducible.

pharmaverse.github.io/logrx ↗

A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.

pharmaverseloggingclinical-trialscompliancer-packagemaintenance
◆Current state
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
◆Where it's heading
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
◆Prediction
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.

◆Recent moves

  1. 3y ago

    Alignment with tidyselect and dplyr changes

    A single-PR release keeping the package working against updated tidyselect and dplyr. Compatibility maintenance, and the last release to date.

    View source ↗
  2. 3y ago

    Release v0.2.1

    A hotfix release whose notes are three merged PRs referenced only by number, so the actual change is not visible from the feed. Labelled a hotfix, which places it as unplanned.

    View source ↗
  3. 3y ago

    Formatted log output plus CRAN readiness work

    A formatted log lands alongside a long run of CRAN check fixes, documentation and pkgdown work. Most of the release is packaging, but the formatted log is what makes the output presentable to a reviewer.

    View source ↗
  4. 4y ago

    Package renamed to logrx; return codes and results writer land

    The release that assembled the package as it exists: axecute() return codes, a results writer, a to_report parameter, logging of unapproved package and function use, and the rename to logrx. Everything after this has been maintenance.

    View source ↗