NNS1-3486: adds ReportingTransactions component to orchestrate dateRange #6026
Conversation
This file contains 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
yhabib
force-pushed
the
NNS1-3486/reporting-component
branch
from
8481297 to
5cfbab5
Compare
dskloetd
reviewed
Dec 17, 2024
yhabib
force-pushed
the
NNS1-3486/reporting-component
branch
from
89b6172 to
f706c63
Compare
dskloetd
approved these changes
Dec 17, 2024
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.
Motivation
Users can filter their export by choosing one of three options: all, this year, or last year.
A follow up PR, will hooked both
ReportingRangeDateSelectorandReportingTransactionsButtonto download transactions for the selected period of time.Changes
ReportingTransactionsto orchestrate downloading transactions for a periodTests
Todos
Not necessary
Prev. PR: #6019