Fix DispatcherScheduler issue with ObserveOn #3497
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
glennawatson
approved these changes
Mar 11, 2023
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #3497 +/- ##
==========================================
+ Coverage 63.83% 64.34% +0.51%
==========================================
Files 157 156 -1
Lines 5768 5702 -66
==========================================
- Hits 3682 3669 -13
+ Misses 2086 2033 -53 see 6 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
FRANKAAAA67
approved these changes
Mar 14, 2023
This comment was marked as spam.
This comment was marked as spam.
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 kind of change does this PR introduce?
Fix for #3495
What is the current behaviour?
Targeting windows10.0.19041.0 exposes System.Reactive base functionality causing issues with ReactiveUI
What is the new behaviour?
When targeting windows10.0.19041.0 ReactiveUI uses System.Reactive base functionality
What might this PR break?
None expected
Please check if the PR fulfils these requirements
Other information: