Skip to content

Allow publication bounds in price history exports - #9

Merged
kvkenyon merged 1 commit into
mainfrom
feat/price-history-publication-bounds
Sep 9, 2026
Merged

Allow publication bounds in price history exports#9
kvkenyon merged 1 commit into
mainfrom
feat/price-history-publication-bounds

Conversation

@kvkenyon

@kvkenyon kvkenyon commented Sep 8, 2026

Copy link
Copy Markdown
Owner

The DAM/RT history-export example previously downloaded all retained sources even when users requested a narrow delivery-date range. Add optional --posted-from and --posted-to bounds so users can explicitly limit publication selection and downloads.

The default still retrieves maximum retained history. Delivery-date filters remain independent and apply after decoding. Documentation explains that publication bounds exclude bundle-only reports without original archive metadata and corrections published outside the chosen range. Invalid publication bounds fail before overwriting the output.

Validation:

  • 35 backfill tests pass, including bounded DAM/RT exports that skip unrelated monthly bundles and preserve the selected archive.
  • Strict mypy passes for 43 source files; Ruff and CLI help pass.
  • An authenticated bounded export retrieves 24 Houston DAM hours for delivery on May 2, 2014, using publications from May 1–2. This is a workflow check, not a new complete-history comparison.

No runtime client or dependency changes. Follow-up to merged #8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant