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

Fix query of protocol params #2558

Merged
merged 2 commits into from
Feb 9, 2024
Merged

Conversation

brentstone
Copy link
Collaborator

@brentstone brentstone commented Feb 7, 2024

Describe your changes

Several PoS params were missing from this query, and the general output is reformatted to look nicer as well.

Indicate on which release or other PRs this topic is based on

v0.31.2

Checklist before merging to draft

  • I have added a changelog
  • Git history is in acceptable state

@brentstone brentstone force-pushed the brent/fix-query-protocol-parameters branch from 7be5724 to d1d00d9 Compare February 7, 2024 19:50
@brentstone brentstone requested a review from tzemanovic February 7, 2024 19:52
brentstone added a commit that referenced this pull request Feb 8, 2024
* brent/fix-query-protocol-parameters:
  changelog: add #2558
  fix query of protocol params
@brentstone brentstone mentioned this pull request Feb 8, 2024
@@ -1538,15 +1538,33 @@ pub async fn query_protocol_parameters(
let pos_params = query_pos_parameters(context.client()).await;
Copy link
Member

Choose a reason for hiding this comment

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

a small improvement - we could use let PosParams { } = query ... syntax to destruct the fields to make sure we're using all so if new one is added we don't miss it here

@tzemanovic tzemanovic merged commit e3932c1 into main Feb 9, 2024
15 checks passed
@tzemanovic tzemanovic deleted the brent/fix-query-protocol-parameters branch February 9, 2024 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants