fix: winningTicketRedeemedEvents query defaults to 100 rows #503
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.
This pull request updates the way transaction and winning ticket events are fetched and merged in the history view, ensuring more accurate pagination and event filtering. The main changes include improvements to the GraphQL query and the merging logic in the React component.
History view data fetching improvements:
transactionsquery (particularly thewinningTicketRedeemedEventspart) to support pagination by adding thefirstandskipparameters, allowing for more flexible and efficient data retrieval. Initially, this simply grabbed the first 100 rows, and would not go beyond this even if the user wanted to see more transactions.