Fix CommandTaskSequenceChaner when exception occurs #1520
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
tomasherceg
approved these changes
Nov 23, 2022
CommandTaskSequenceHelper is used when you use `;` operator in a command binding. We used to chain the tasks using ContinueWith which (counterintuitively) continues even exception occurs. So when you called a `method1(); ...` it would silence exceptions from method1.
exyi
force-pushed
the
fix-exception-task-chaining
branch
from
9650717
to
6c8cbc9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CommandTaskSequenceHelper is used when you use
;operator in a command binding. We used to chain the tasks using ContinueWith which (counterintuitively) continues even exception occurs. So when you called amethod1(); ...it would silence exceptions from method1.