-
Notifications
You must be signed in to change notification settings - Fork 70
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
Go: Implementing List commands #2370
Go: Implementing List commands #2370
Conversation
Signed-off-by: Janhavi Gupta <[email protected]>
// | ||
// Return value: | ||
// The Result[string] containing the value of the first element. | ||
// If key does not exist, [api.CreateNilStringResult()] will be returned. |
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.
// If key does not exist, [api.CreateNilStringResult()] will be returned. | |
// If key does not exist, `nil` will be returned. |
For the end user it does not matter where null comes from. We should describe what returned and when.
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.
Here, the api.CreateNilStringResult()
is returning nil
object, whereas it's returning api.Result[string]{val: "", isNil: true}
object. To not make it too verbose, we decided to replace it with a function and link in the docs.
Please let me know if you think otherwise. Going ahead with the merge for now, I can address any change required in the next PR.
Signed-off-by: Janhavi Gupta <[email protected]>
Implementing the following List commands: