Allow publication bounds in price history exports - #9
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The DAM/RT history-export example previously downloaded all retained sources even when users requested a narrow delivery-date range. Add optional
--posted-fromand--posted-tobounds 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:
No runtime client or dependency changes. Follow-up to merged #8.