Feature/transaction #326
Merged
Feature/transaction #326
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Running Lighthouse audit... |
1 similar comment
|
Running Lighthouse audit... |
crypto-engineer
force-pushed
the
feature/transaction
branch
from
3613a8c
to
d96712a
Compare
crypto-engineer
commented
Jun 8, 2022
src/pages/Dashboard/sub-pages/IssueRequests/IssueRequestsTable/index.tsx
Show resolved
Hide resolved
peterslany
reviewed
Jun 9, 2022
crypto-engineer
force-pushed
the
feature/transaction
branch
from
c41fb67
to
1b644d6
Compare
peterslany
approved these changes
Jun 9, 2022
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.
The requested feature is to create a page where we can see the details of a transaction e.g. issue request, redeem request, replace request.
/transaction/:transactionType/:transactionHashwheretransactionTypecan beissue,redeem, &replaceandtransactionHashis a transaction hash. On that page, we display the necessary details of that transaction.For this feature request @gregdhill made, I implemented routing and page structures in the first place.
