hubValidations 0.13.0

Enhancements

• Added validation warning infrastructure for informational messages that don't affect validation results (#292).
  • validate_pr() now displays a warning when hub config files are modified in a pull request, alerting maintainers to review changes that may affect validation of existing data.
  • Validation-level warnings are displayed prominently in a box at the top of print output.
  • Check-level warnings can be displayed inline with their checks using print(x, show_check_warnings = TRUE).
  • check_for_errors() gains a show_warnings parameter to control display of check-level warnings.
• Enhanced target data column validation to support target-data.json configuration (#280).
  • check_target_tbl_colnames() and check_target_tbl_coltypes() now use deterministic validation when target-data.json config is available, with error messages explicitly referencing the config file.
• Enhanced check_target_tbl_rows_unique(), check_target_tbl_output_type_ids(), and check_target_tbl_oracle_value() to support target-data.json configuration (#282).
• Fixed bug where the as_of column was incorrectly included in oracle-output validation grouping. Oracle data is designed to contain a single version per observable unit with a one-to-one mapping to model output data, so including as_of in uniqueness checks could introduce false positives (#282).
• Added date_col parameter support for oracle-output target data validation (#290).
  • check_target_tbl_coltypes(), check_target_dataset_rows_unique(), and read_target_file() now pass date_col to oracle-output schema and connection functions, providing consistent handling of partitioned date columns across both time-series and oracle-output target types.
  • When target-data.json config exists, user-provided date_col is ignored and the config value is used instead.
• check_target_tbl_values() now supports relaxed date validation for time-series target data (#274).
  • When allow_extra_dates = TRUE, date values are not required to match tasks.json, allowing historical observations while validating other task IDs strictly. This behavior is controlled by the new allow_extra_dates parameter (default FALSE).
  • Oracle-output target data always uses strict validation regardless of the allow_extra_dates setting.
  • Date column identification is deterministic: extracted from target-data.json config when available, otherwise from the date_col parameter.
  • The allow_extra_dates parameter is also available in validate_target_data(), validate_target_submission(), and validate_target_pr().