core: actions, query: expose limit param for getOrderHistory & getTaskHistory #149
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
sehyunc
approved these changes
Jan 8, 2025
akirillo
force-pushed
the
andrew/task-history-len-param
branch
from
236530c to
5e9979f
Compare
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.
This PR makes the
getOrderHistoryandgetTaskHistoryactions / queryFns configurable with the desired response length. The API already supports this, so this is not dependent on any relayer changes.Testing
This was tested with a local frontend running against the mainnet stack, where I asserted that transfer history going further back could be fetched.