-
-
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: Make ReactiveList obselete and promote DynamicData #10
Comments
This change is happening in the next few days. |
@glennawatson @RolandPheasant |
Documentation was my caveat when I tried to convert current project where ReactiveList behave strangely with DynamicData. It would be great to create a sample project to demonstrate usage. |
https://github.com/RolandPheasant/DynamicData/wiki/Introduction-for-ReactiveUI-users is some documentation that Roland prepared a while back.
|
We should definitely make sure users see that article. |
I'm looking at upgrading an "old" Xamarin.Android-based ReactiveUI and due to the obsolete nature of ReactiveList and that there is no "legacy" version of ReactiveRecyclerViewAdapter/ReactiveList (have to use IObservable<IChangeSet> now), I'm really confused on how to re-structure this app to use DynamicData, so: Are there any sample projects using Xamarin.Android ReactiveUI/DynamicData? TIA... |
Jump on slack https://reactiveui.net/slack and join the #ReactiveUI channel. Someone can help you adapt your project there. You can still use ReactiveList with the There is a second generic class with the signature so you can derive off That will call the DynamicData overload |
That overload class can handle any collection derived from |
This relates to reactiveui/ReactiveUI#1372
Summary: Move the ReactiveList based series of classes to the Legacy namespace and mark them obsolete and direct them to the DynamicData (DD) github page.
Reason: The ReactiveList classes are getting a bit clumsy and the DD framework is much more powerful. It has a API more inline with the Rx style of doing things. Roland Pheasant is also very active on the project. By making ReactiveList redundant it will allow the core developers and contributors to focus on the more critical functionality.
Side effects: The potential side effect is projects relying on the ReactiveList. Although the ReactiveList will still be available it's not immediately straight forward how to do the conversion. Also can be a impact on @RolandPheasant with a increased user base.
The text was updated successfully, but these errors were encountered: