-
Notifications
You must be signed in to change notification settings - Fork 607
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
x/lock: Fix ExtendLockup
API
#1937
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexanderbez
approved these changes
Jul 1, 2022
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.
We should have a changelog for this IMO
ValarDragon
reviewed
Jul 1, 2022
ValarDragon
reviewed
Jul 1, 2022
ValarDragon
approved these changes
Jul 1, 2022
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.
LGTM, but lets add a Go API changelog entry
p0mvn
approved these changes
Jul 1, 2022
thanks for adding the chnage log and merging! |
mergify bot
pushed a commit
that referenced
this pull request
Jul 12, 2022
* Fix extendlock api * Apply suggestions from code review * Add changelog Co-authored-by: Dev Ojha <[email protected]> Co-authored-by: Dev Ojha <[email protected]> (cherry picked from commit 99304f2) # Conflicts: # CHANGELOG.md
mattverse
added a commit
that referenced
this pull request
Jul 12, 2022
* x/lock: Fix `ExtendLockup` API (#1937) * Fix extendlock api * Apply suggestions from code review * Add changelog Co-authored-by: Dev Ojha <[email protected]> Co-authored-by: Dev Ojha <[email protected]> (cherry picked from commit 99304f2) # Conflicts: # CHANGELOG.md * Fix merge conflict: changelog Co-authored-by: Matt, Park <[email protected]> Co-authored-by: mattverse <[email protected]>
ValarDragon
added a commit
that referenced
this pull request
Aug 1, 2022
This reverts commit bd32316.
ValarDragon
added a commit
that referenced
this pull request
Aug 3, 2022
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A:backport/v10.x
backport patches to v10.x branch
C:docs
Improvements or additions to documentation
C:x/lockup
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sub-component of: #1838
What is the purpose of the change
The current
ExtendLockup
API directly takes in the lock object as a pointer as its parameter. This PR changes this existing API to take in lock ID to improve safety for this APIBrief Changelog
Improve
ExtendLockup
API safety.Documentation and Release Note
Unreleased
section inCHANGELOG.md
? no