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

Show current bundle info #34

Merged
merged 7 commits into from
Nov 9, 2023
Merged

Show current bundle info #34

merged 7 commits into from
Nov 9, 2023

Conversation

torkelrogstad
Copy link
Collaborator

image

// https://github.com/LayerTwo-Labs/testchain/blob/ba78df157fcb9f85d898f65db43c2842ab9473ff/src/policy/corepolicy.h#L25
static const double maxWeight = (maxStandardTxWeight / witnessScaleFactor) / 2;

Map<String, dynamic> get _values => {
Copy link
Collaborator

@octobocto octobocto Nov 8, 2023

Choose a reason for hiding this comment

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

Is there a reason you cherry-pick fields here? Why not show all of them, always? Future-proofs it. Will never have to look it up in the rpc

Copy link
Collaborator

@octobocto octobocto Nov 8, 2023

Choose a reason for hiding this comment

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

If it is the suffixes you want, you could create a withSuffix() function that looks at the key, and appends a fitting suffix

value: withSuffix(key, _values[key])

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm just following the design spec 🫡

width: width,
child: SailText.secondary12(label),
),
if (label != null)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we really want this? Should figure out a fitting label instead imo. Can't see it used anywhere

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I use it for the yet-to-be-bundled withdrawals

@torkelrogstad torkelrogstad merged commit 310f4d3 into master Nov 9, 2023
1 check passed
@torkelrogstad torkelrogstad deleted the 2023-11-08-bundle branch November 9, 2023 08:31
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