Fix for ignored async superstate transitions when child state has unmet guard #631
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.
This PR is for issue #629 in which a parent state transition is ignored when:
FireAsync.When the synchronous call to
Fireis used instead, it selects the nearest ancestor that has a transition with no unmet guard conditions.This PR also includes some housekeeping changes:
#if TASKSdirectives.AsyncFiringModesFixturefromvoidtoasync Task.TransitionTestsinto sync and async test classes.