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
Update storage.GuaranteedUpdate
to be clearer
#109514
Update storage.GuaranteedUpdate
to be clearer
#109514
Conversation
Hi @aryan9600. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
/assign @MikeSpreitzer @lavalamp |
@@ -69,28 +69,28 @@ func (s *DryRunnableStorage) GetList(ctx context.Context, key string, opts stora | |||
} | |||
|
|||
func (s *DryRunnableStorage) GuaranteedUpdate( | |||
ctx context.Context, key string, ptrToType runtime.Object, ignoreNotFound bool, | |||
ctx context.Context, key string, out runtime.Object, ignoreNotFound bool, |
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.
This is like, memory to store the object in that has the right type. I don't think "out" is a good name for that.
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 thought out
would be fine as that's where the actual output of operations executed in Get()
and GuaranteedUpdate()
gets stored. What would you rather we change it to?
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.
It's a hard question!
The reason this is an input parameter is because this function needs to know the type to use, there's no way for it to construct a variable of the right type. That we also use this to store the result is accidental -- if that were the primary purpose here, we'd return that as an output parameter.
The best I can come up with at the moment is resultDestination
or maybe just destination
but I'm not in love with that, either.
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.
"memory to store the object" sounds a lot like output!
And yes, this is also being used to input the type.
I think both resultDestination
and destination
are fine and sufficient improvements to ptrToType
.
…earer. Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
21a95e2
to
f8df26a
Compare
/retest-required |
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
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aryan9600, lavalamp, MikeSpreitzer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Sanskar Jaiswal jaiswalsanskar078@gmail.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Makes the description of
storage.Interface.GuaranteedUpdate
clearer and accurate. RenamesptrToType
toout
ptrToType
todestination
, to better convey the functionality of the argument.Which issue(s) this PR fixes:
Fixes #107534
Does this PR introduce a user-facing change?