Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update ReactiveUI to use Reactive Extensions 4.0.0 as minimum #1701

Merged
merged 5 commits into from Aug 3, 2018

Conversation

glennawatson
Copy link
Contributor

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixes #1672

This changes the min version for ReactiveUI to use Rx 4.0.0

We are getting a few reports from users where upgrading to Rx 4.0.0 fixes their issues.

Also adding .NET .Core 2.1 as a target. It was partially done in a previous PR but this adds it to the other projects.

What is the current behavior? (You can also link to an open issue here)

Use Rx 3.1.1

What is the new behavior (if this is a feature change)?

Use Rx 4.0.0 and also .NET Core 2.1 added to other projects.

What might this PR break?
Users using Rx 3.1.1. will have to upgrade their package reference in nuget.

@glennawatson glennawatson requested review from a team August 2, 2018 19:39
<ProjectReference Include="..\ReactiveUI\ReactiveUI.csproj" />
</ItemGroup>

<ItemGroup Condition=" '$(TargetFramework)' == 'Xamarin.Mac20' ">
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to reference netstandard to get the Xamarin.Mac20 to compile after updating. Bit weird.

@clairernovotny
Copy link
Member

You should not need a netcoreapp2.1 target unless you're using new API's there (like Span<T>).

@glennawatson
Copy link
Contributor Author

Would it not make it easier for consuming users to have a .NET Core 2.1? Or would the JIT just go based on their API? Also my understanding is also they done a ton of performance operations on .NET Core 2.1 so potentially users targetting the framework could take advantage.

@clairernovotny
Copy link
Member

.NET Core 2.1 is just an API surface area. It's no different than releasing .NET 4.6 and 4.6.1 at the same time. No need to unless you're using API's not in the lower version.

@glennawatson
Copy link
Contributor Author

Removed that platform until we need it then. Thanks for the info.

@glennawatson glennawatson changed the title feat: Update ReactiveUI to use Reactive Extensions 4.0.0 as minimum and add .NET Core 2.1 feat: Update ReactiveUI to use Reactive Extensions 4.0.0 as minimum Aug 3, 2018
Copy link
Member

@olevett olevett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@glennawatson glennawatson added this to the vNext milestone Aug 3, 2018
@glennawatson glennawatson merged commit 56b52f7 into master Aug 3, 2018
@glennawatson glennawatson deleted the glennawatson-rx4 branch August 3, 2018 15:10
glennawatson added a commit that referenced this pull request Mar 23, 2019
 
feat: Update ReactiveUI to use Reactive Extensions 4.0.0 as minimum (#1701)

* Updated references to system.reactive to 4.0.0
@lock lock bot locked and limited conversation to collaborators Jun 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update RxUI to use System.Reactive >= 4
3 participants