Improved await support of ReactiveProperty, ReactiveCommand #86
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.
I've fully refactored await support of ReactiveProperty and ReactiveCommand.
It can handle
CancellationToken
correctly and addGetAsyncHandler
that can reuse(zero-allocate) await event.Changed push event to awaiter from internal to external.
Breaking Change:
AsyncReactiveCommand
does not support await.how to use from
awaitable.md
Awaitable
You can use
await
operator toReactiveProperty
(includes Slim),ReadOnlyReactiveProperty
(includes Slim),ReactiveCommand
.When use
await
operator to them, then wait a next value will be published.For example:
If you await multiple times, you should get
ObservableAsyncHandler<T>
fromGetAsyncHandler
. it can await multiple times on zero allocation. If you await single time, you can useawait command.WaitUntilValueChangedAsync(token)
.