-
Notifications
You must be signed in to change notification settings - Fork 610
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: adding UpdateStateOnMisbehaviour to ClientState interface #1198
feat: adding UpdateStateOnMisbehaviour to ClientState interface #1198
Conversation
Co-authored-by: colin axnér <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay! Nice work!
We should add changelog entries for each function we add/remove from the ClientState interface. We can catch any missed changelog entries during a changelog audit
@@ -26,7 +26,8 @@ func (cs ClientState) CheckHeaderAndUpdateState( | |||
|
|||
foundMisbehaviour := cs.CheckForMisbehaviour(ctx, cdc, clientStore, msg) | |||
if foundMisbehaviour { | |||
return cs.UpdateStateOnMisbehaviour(ctx, cdc, clientStore) | |||
cs.UpdateStateOnMisbehaviour(ctx, cdc, clientStore) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this function will be deleted soon enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah nvm! I see the return right below now!
…os#1198) * feat: adding UpdateStateOnMisbehaviour to ClientState interface * Update modules/core/exported/client.go Co-authored-by: colin axnér <[email protected]> * fix: return values * chore: changelog Co-authored-by: colin axnér <[email protected]>
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview closes: cosmos#607 <!-- Please provide an explanation of the PR, including the appropriate context, background, goal, and rationale. If there is an issue with this information, please provide a tl;dr and link the issue. --> ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [ ] New and updated code has appropriate documentation - [ ] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [x] Linked issues closed with keywords --------- Co-authored-by: Manav Aggarwal <[email protected]>
Description
closes: #1193
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes