-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
RFC: What are pain points with the ReactiveUI project as a user? #13
Comments
It would cool to see support for custom DI-containers, as everyone adheres to their favorite. |
UWP navigation...it's view-first and the way RxUI has implemented the VM-first approach has killed the niceness of the transition animations. It's currently just a flat-out hide/show approach. |
Confusing threading exceptions when I referenced the |
Coming from the perspective of the ReactiveUI book (which is great by the way), the first section says to just do an “Install-Package ReactiveUI”. The book mentions that the “bait and switch” technique should take care of the dependencies. However, doing this in a top-level WPF platform project is not enough. The nuget package targets System.Reactive (>= 4.0.0), but Glen mentioned that at the moment RxUI is using System.Reactive 3.1.1 and you need to add a reference to System.Reactive.Compatibility til the next release of RxUI. I’m new to this, but just getting started with the build configuration currently published is not straightforward at all (at least with respect to WPF). Diving into this great library more every day. |
BTW ReactiveUI 8.4.1 was released this morning that has System.Reactive at 4. |
The reasoning for the new ReactiveUI.WPF is Visual Studio for Mac unfortunately. https://reactiveui.net/blog/2018/05/reactiveui-v8.0.0-released
|
Getting reactiveui/ReactiveUI#1598 shipped will help folks out heaps. |
What are your pain points at the moment with RxUI?
Tell me and reply to this issue.
The text was updated successfully, but these errors were encountered: