Skip to content
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

Add missing data to Consensus tx list #1462

Merged
merged 2 commits into from
Jun 28, 2024
Merged

Add missing data to Consensus tx list #1462

merged 2 commits into from
Jun 28, 2024

Conversation

buberdds
Copy link
Contributor

@buberdds buberdds commented Jun 27, 2024

Provide data for transactions list to and value columns.

side note: these columns will be merged into Details column when designs are ready

Copy link

github-actions bot commented Jun 27, 2024

Deployed to Cloudflare Pages

Latest commit: b857bd813fbd278a6852b35b88acefbb06ea3f46
Status:✅ Deploy successful!
Preview URL: https://9c96f48f.oasis-explorer.pages.dev

@buberdds buberdds force-pushed the mz/consensusTxList branch 2 times, most recently from fb98cf9 to 3390cbb Compare June 27, 2024 11:29
@buberdds buberdds force-pushed the mz/consensusTxList branch from 3390cbb to b857bd8 Compare June 27, 2024 11:34
>

const tableRows = transactions?.map(transaction => {
const targetAddress = transaction.body.to || transaction.body.account
Copy link
Contributor Author

@buberdds buberdds Jun 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Transactions consensus and runtime APIs are not consistent:

runtime has props

amount?: string;
to?: Address;

where here we use body. not sure this should be unified in Nexus. Current API might work fine with new design where we will have to render different body props depends on a tx type.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say it would be nice to unify, but not high priority. Let's make it work on our side, and BE can resolve it, once they find the time.

@buberdds buberdds marked this pull request as ready for review June 27, 2024 11:52
const tableRows = transactions?.map(transaction => {
const targetAddress = transaction.body.to || transaction.body.account
return {
key: `${transaction.hash}${transaction.index}`,
Copy link
Collaborator

@lubej lubej Jun 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for ${transaction.index} I think. Tx hash should be unique enough, unless there is a case, where it's missing or duplicated.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was needed in the past #1412

@buberdds buberdds merged commit 1e685dd into master Jun 28, 2024
8 checks passed
@buberdds buberdds deleted the mz/consensusTxList branch June 28, 2024 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants