Don't mention MultiOperation in Update-with-Start error #7826
Conversation
This file contains hidden or 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
stephanos
changed the title
ychebotarev
approved these changes
May 29, 2025
Contributor
|
Nice developer 💌 , thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changed?
Always say "Update-with-Start" in the error message returned to the user when using MultiOperations.
(internally, History will still use MultiOperation in the error messages)
Why?
Users wouldn't (and shouldn't) know that Update-with-Start happens to be a MultiOperation.
How did you test it?
Potential risks
I don't expect any users to match on that string. There might be SDK tests that break now; I'll have to follow up on that.