Pool transactions: clearer table and infinite scroll#127
Open
Jiangzhewen wants to merge 1 commit into
Open
Conversation
Author
|
Local validation completed:\n\n- npm ci\n- npm run build\n- Browser check on /pool with a Playwright route mock for /pool/transactions: verified 50 initial rows and append to 75 after scrolling.\n\nThe Vercel check is currently failing with "Account is blocked", which appears unrelated to this code change. |
Author
|
Vercel is failing before it reaches the project build with |
This file contains hidden or 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
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.
Summary
getPoolTransactionsAPI path using the existingdataEndpointand/pool/transactionsendpoint.Validation
npm cinpm run buildhttp://127.0.0.1:5000/pool/pool/transactionsverified 50 initial rows and scroll append to 75 rows.Note: in this local environment,
https://data.cap.iorequests fail during TLS setup and the existing Alchemy key returns 403, so live API/RPC responses could not be validated from this machine. The mocked browser check only replaced the pool transactions API response.Closes #29