-
Notifications
You must be signed in to change notification settings - Fork 9
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
Enable pagination in Events lists #1489
Conversation
Deployed to Cloudflare Pages
|
if (layer === Layer.consensus) { | ||
throw AppErrors.UnsupportedLayer | ||
} | ||
const eventsQuery = useGetRuntimeEvents(network, layer, { | ||
tx_hash: transaction.hash, | ||
limit: 100, // We want to avoid pagination here, if possible |
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.
Why we want to avoid pagination and why we set 100 cap?
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.
Related: #226
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.
🤷 I can't find an explanation. 1000 limit was allowed when #224 was made
e549858
to
0e1ebc9
Compare
requested by Tadej, but I am not sure we should do it looking at comments
random test urls
tx
https://dc9c017d.oasis-explorer.pages.dev/mainnet/sapphire/tx/0x9ce91f01d822bb4144de04ad4fce4711eb005c7d2824bfe38f670bf2916727ca
addr
https://dc9c017d.oasis-explorer.pages.dev/mainnet/sapphire/address/oasis1qry5d5zxs58w9deu5ara5zaamhkzqtg99s00ls90/events
block
https://dc9c017d.oasis-explorer.pages.dev/mainnet/sapphire/block/4683703/events