-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement pagination by tx hash for requesting of transaction history #2940
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor comments.
Feedback from @sisou: for backwards-compatibility, it would be better to have new functions for the pagination and keep the old ones. |
It feels a bit ambiguous to have a one method that supports and one which doesn't support the |
This only applies to the web-client and his reasoning is that you always have to provide null for options if you don't want to pass them. But then, there are two |
9a8138d
to
1ac7b09
Compare
The problem with having to send |
Rebasing branch to merge it |
1ac7b09
to
a63bc0d
Compare
What's in this pull request?
This PR adds a
start_at
parameter to various functions used to request the transaction history.This efficiently adds pagination of results from a known transaction hash (which will not be included in subsequent queries).
@sisou This changes the interface slightly, adding a new parameter. It would be good to have your input on this.
This fixes #2697, #2733, #2247.
Pull request checklist
clippy
andrustfmt
warnings.