Skip to content

Conversation

@ghuntley
Copy link
Member

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

Feature

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

System.Reactive is pinned to v3.x, preventing installation of v4.x

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

System.Reactive is unpinned.

What might this PR break?

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Other information:

I have not tested this change; it's a pure find and replace.

@ghuntley
Copy link
Member Author

In theory, this is all that is needed to be done.

screen shot 2018-06-12 at 12 49 16 pm

@ghuntley ghuntley merged commit 51604d5 into master Jun 12, 2018
@ghuntley ghuntley deleted the enable-rxnet-4 branch June 12, 2018 09:04
@jasonwurzel
Copy link
Contributor

jasonwurzel commented Jun 30, 2018

Hi @olevett @ghuntley , I have to chime in here because I'm having some trouble using Rx 4 alongside RxUI 8.3.1 (for a short description, please see https://reactivex.slack.com/archives/C02AJB872/p1530353295000001 ) . Would you mind to explain this PR to me? For me the change looks like NOW RxUI is pinned to Version 3.1.1 of System.Reactive, as before any version from 3.1.1 to 4 could be used...thank you for explaining.

@glennawatson
Copy link
Contributor

Before it meant use 3.11 but only allow projects to use below 4.0.0 using binding redirects without producing an error.

@jasonwurzel
Copy link
Contributor

hey Glenn, thank you for the clarification and the Link in Slack! Much appreciated.

glennawatson pushed a commit that referenced this pull request Mar 23, 2019
 
feature: enable reactiveui with system.reactive v4 (#1674)
@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.

5 participants