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.
#39
If it's okay, I'd like to hear your opinions (on Twitter as well) @runceel, @xin9le
I have prepared a class that implements INotifyPropertyChanged and INotifyDataErrorInfo for binding in XAML.
In runceel/ReactiveProperty, the relationship seems to be such that ReactiveProperty becomes ReactivePropertySlim, and BindableReactiveProperty becomes ReactiveProperty.
In R3, since ReactiveProperty is a Subject (BehaviorSubject) and does not stop on OnError, I made it so that calling OnErrorResume from outside will set an error flag.
It would be good if OnErrorResume is called from external validation or error streams.
For clearing the error, I thought it would be sufficient to have ResetError called separately.
Would this approach work without issues in WPF (or other XAML platforms)?