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 details column to Consensus transactions list #1472

Merged
merged 10 commits into from
Jul 25, 2024
Merged

Conversation

buberdds
Copy link
Contributor

@buberdds buberdds commented Jul 5, 2024

  • adds details row. The way how each method details will look like is not defined yet and we will narrow this down during a meeting (handle more types via getConsensusTransactionDetails)
  • currently older transactions are not correctly indexed by Nexus. Older txs will show empty details in most cases, but recent one are Ok for testing

TODO:

  • keep hash column

Copy link

github-actions bot commented Jul 5, 2024

Deployed to Cloudflare Pages

Latest commit: 3aaf1560588dd7625a822d9491e44471569ad3bb
Status:✅ Deploy successful!
Preview URL: https://acc26250.oasis-explorer.pages.dev

@buberdds buberdds force-pushed the mz/newtxList branch 2 times, most recently from f908397 to cc002d4 Compare July 5, 2024 10:13
@buberdds buberdds marked this pull request as ready for review July 5, 2024 10:24
@buberdds
Copy link
Contributor Author

buberdds commented Jul 9, 2024

Not ready for review. Need to talk to Don first.

@buberdds buberdds changed the title Add details column to Consensus transactions list WIP: Add details column to Consensus transactions list Jul 9, 2024
@buberdds buberdds force-pushed the mz/newtxList branch 7 times, most recently from 2e84e7b to ce95725 Compare July 17, 2024 15:28
@buberdds buberdds changed the title WIP: Add details column to Consensus transactions list Add details column to Consensus transactions list Jul 19, 2024
return (
<>
<From address={transaction.sender} ownAddress={ownAddress} scope={scope} />
<LabelValue label={t('common.id')} value={transaction.body?.id} trimMobile />
Copy link
Member

Choose a reason for hiding this comment

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

This can be matched to runtime ids

runtimeId: '000000000000000000000000000000000000000000000000f80306c9858e7279',

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes body.id is always runtime id in executor commits. Why should I match this value with a config value?

Copy link
Contributor Author

@buberdds buberdds Jul 25, 2024

Choose a reason for hiding this comment

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

discussed during sync meeting:

  • define tx details and labels (planning meeting)
  • map runtime id to a name (separate PR)
  • use ValidatorLink instead AccountLink where needed

@buberdds buberdds merged commit 1651e1a into master Jul 25, 2024
8 checks passed
@buberdds buberdds deleted the mz/newtxList branch July 25, 2024 14:32
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