Changelog
Source:NEWS.md
qryflow (development version)
Breaking Changes
The
sourceargument has been removed fromqryflow_execute(). Source information is now stored automatically in chunk metadata during parsing.qryflow_default_type()has been removed as a standalone exported function. Default type is now controlled directly via thedefault_typeargument inqryflow(),qryflow_run(), andqryflow_parse(), or through the global optionoptions(qryflow.default_type = "query"). Note: the option key has changed fromqryflow.default.typetoqryflow.default_type.
New Features
on_errorargument added toqryflow(),qryflow_run(), andqryflow_execute(). Controls behavior when a chunk fails during execution. Accepts"stop"(default, halts immediately),"warn"(signals a warning and continues), or"collect"(runs all chunks and reports all errors together at the end). (#11 and #12verboseargument added toqryflow(),qryflow_run(), andqryflow_execute(). WhenTRUE, emits a progress message before each chunk and a summary upon completion showing total runtime, successes, errors, and skipped chunks. Defaults toFALSE. Can be enabled globally withoptions(qryflow.verbose = TRUE). ([#8])default_typeargument added toqryflow(),qryflow_run(), andqryflow_parse(). Determines the chunk type assigned to untagged chunks. Defaults to"query". Can be set globally withoptions(qryflow.default_type = "query").qryflow_meta()is now an exported function for accessing execution metadata (status, duration, start/end times, error messages) from bothqryflowworkflow objects and individualqryflow_chunkobjects.validate_con_arg()is now called internally byqryflow_execute()to provide clear, actionable error messages when the connection argument is missing, invalid, or disconnected.Workflow-level execution status is now tracked and stored in metadata. A completed workflow is assigned a status of
"success"if all chunks succeeded, or"partial"if any chunk encountered an error.
Internal Changes
Combined
qryflow_workflowandqryflow_resultsinto single object. ([#14])Added
cli.Rwith verbose helpers (report_workflow_start(),report_chunk_start(),report_chunk_end(),report_workflow_end()).Added
on-error.Rconsolidating error dispatch logic (validate_on_error(),dispatch_on_error(),dispatch_collected_errors()) supporting the newon_errorargument.Metadata handling has been refactored into
meta.R, centralizing time tracking and duration formatting used across workflow and chunk objects.Updated documentation, vignettes, and README to reflect new arguments and removed functions.
qryflow 0.3.0
Breaking Changes
The type-specific parser system has been removed (#13) .
register_qryflow_parser(),ls_qryflow_parsers()validate_qryflow_parser(), andqryflow_parser_exists()are no longer available. Custom chunk behaviour should now be implemented entirely through handlers. Seeregister_qryflow_type()for details.ls_qryflow_handlers()andregister_qryflow_handler()were removed. Usels_qryflow_types()andregister_qryflow_type()instead.
Internal Changes
Parsing is now handled by a single unified parser that produces a consistent
qryflow_chunkstructure regardless of chunk type. This replaces the previous system where each chunk type could define its own parsing logic.User provided duplicate names now generates an error via refactored approach to
fix_chunk_names()(Now,resolve_chunk_names())Updated documentation, README, and vignettes to accomodate unified parsing.
qryflow 0.2.0
CRAN release: 2026-02-05
Breaking change:
qryflow(),qryflow_run(),qryflow_execute()and internal functions now acceptconargument first, before thesql/workflowarguments. This makes the API consistent with DBI and other DB packages, improves ergonomics, and enables method dispatch on connection classes. (#5)Minor documentation updates (#2)
Update License Year (#6)