-
Notifications
You must be signed in to change notification settings - Fork 24
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
Discuss: Minimize Observable
interface into...
#10
Comments
+1 on having an interface designed for consumers rather than implementors. My first exposure to Observable (on both sides) had a steep learning curve because of the large surface area. I'm less sure about the consequences of making it generic. Should we separate those discussions? |
love it! |
Sure we can split into sub-issues. Intended generic use: abstract class ObservableList<T> implements List<T>, Observable<ListChangeRecord<T>>> {} Instead of the current: abstract class ObservableList<T> implements Observable {
// Let us be honest, if you are listening to an observable list, you want this one.
Stream<List<ListChangeRecord<T>> get listChanges;
} |
You've convinced me on the generic argument as well 😃 |
I'm closing based on this already being underway. |
YAY! |
Underway? |
Reopening and assigning to myself since these changes were reverted in 0.21.0 when the package was migrated to Dart 2. |
The text was updated successfully, but these errors were encountered: