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

feat: add new query for pending nonces using chain id #1131

Merged
merged 7 commits into from
Sep 20, 2023

Conversation

kingpinXD
Copy link
Contributor

Description

Adds anew query PendingNoncesByChain

Closes:

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

  • Tested CCTX in localnet
  • Tested in development environment
  • Go unit tests
  • Go integration tests
  • Tested via GitHub Actions

Checklist:

  • I have added unit tests that prove my fix feature works

Copy link
Member

@lumtis lumtis left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +260 to +267
message QueryPendingNoncesByChainRequest {
uint64 chain_id = 1;
}

message QueryPendingNoncesByChainResponse {
PendingNonces pending_nonces = 1 [(gogoproto.nullable) = false];
}

Copy link
Member

Choose a reason for hiding this comment

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

Not a very big deal but maybe we might want to keep the same order for message definitions as rpc endpoint definitions above

@kingpinXD kingpinXD merged commit a5d704b into develop Sep 20, 2023
18 of 19 checks passed
@lumtis lumtis deleted the query-pending-nonces-by-chainID branch October 27, 2023 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants