-
Notifications
You must be signed in to change notification settings - Fork 300
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 Pop Receipt #1066
Update Pop Receipt #1066
Conversation
Hi @wsugarman, just to confirm, is this PR ready to be merged? |
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.
Just a small question
@@ -59,10 +59,10 @@ await this.queueClient | |||
this.stats.MessagesSent.Increment(); | |||
} | |||
|
|||
public async Task UpdateMessageAsync(QueueMessage queueMessage, TimeSpan visibilityTimeout, Guid? clientRequestId = null, CancellationToken cancellationToken = default) | |||
public async Task<UpdateReceipt> UpdateMessageAsync(QueueMessage queueMessage, TimeSpan visibilityTimeout, Guid? clientRequestId = null, CancellationToken cancellationToken = default) |
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.
@wsugarman: is there a reason not to put the the popReceipt-updating logic here (in UpdateMessageAsync
)? I think I'd rather have it here than sprinkled all throughout the callers, where I think it's more likely for folks to forget that they need to capture the output and manually update the receipt.
I think you could change the parameter types here to update the message object in-place
Update the pop receipt for messages once they have been updated.