-
Notifications
You must be signed in to change notification settings - Fork 7
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
Improve token transfer listing for tokens #738
Conversation
Deployed to Cloudflare Pages
|
4ff0aad
to
284c539
Compare
7cfedae
to
7507ce1
Compare
OK, see #743 |
ad7c964
to
3e7f427
Compare
Done. |
Abstract away more things and centralize them in the pagination engine, so that the pagination engine is in a position where it could do some more sophisticated stuff, like decoupling client-side and server-side behavior.
... of ComprehensiveSearchParamsPagination No actual behavior is changed yet, just copied and renamed.
293902e
to
262a7e2
Compare
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.
Looks easily reversible when we stop needing it
switch (candidates.length) { | ||
case 0: | ||
throw new Error('Data not found!') | ||
case 1: |
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.
With strict types this could be ensured at compile time, but not worth inventing it for this temporary workaround until backend adds filtering by signature
This first implementation only loads the first batch from the server, and the works with that data.
262a7e2
to
7de4f79
Compare
Yes, there is |
This depends on #743.Improve pagination experience by proving rudimentary client-side pagination (limitation: looking only at the first 1000 records)
This impacts two pages:
/mainnet/sapphire/token/0x998633BDF6eE32A9CcA6c9A247F428596e8e65d8
)/mainnet/sapphire/address/0x998633BDF6eE32A9CcA6c9A247F428596e8e65d8/token-transfers#transfers
I think there is some problem with the pagination widget sometimes displaying the wrong number of total pages, but that is totally unrelated.Update: workaround added for anomalous behavior.Technical note: great emphasis has been placed in developing this in separate commits so that it's easier to follow what is going on, so I suggest reviewing commit by commit.