feat: add pagination to tx list #895
Open
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
|
@im-adithya what is the status of this one? |
im-adithya
commented
Feb 18, 2025
| return <TransactionItem key={tx.paymentHash + tx.type} tx={tx} />; | ||
| {transactions?.map((tx, i) => { | ||
| return ( | ||
| <TransactionItem key={tx.paymentHash + tx.type + i} tx={tx} /> |
There was a problem hiding this comment.
Should we use updatedAt in TransactionItem component instead of tx.settledAt || tx.createdAt
There was a problem hiding this comment.
And for failed transactions we can maybe have initiated time in the tx dialog as well
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.
Fixes #29
Needs some more testing, drafting till then