You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to start my discussion as I came to this library, years ago, as an Android Developer, Rx(n)s work the same way than LiveData. This is based on a MVVM structure, but when the base for Android was to do something like (this would be done in Kotlin but I'll translate it into Dart, respecting the Android words):
abstract class MyController extends GetxController {
LiveData<T?> get reactiveLiveData;
}
class MyControllerImpl extends MyController {
@override
final MutableLiveData<T?> reactiveLiveData = MutableLiveData();
}
this way, the view of reactiveLiveData would be immutable from the UI, which is the base of MVVM: UI listens to reactions to the ViewModel (in our case, our GetxController).
Would it be interesting to create a parent class of Rx and Rxn that is immutable from the UI point of view?
I have been working with many developers who claimed to have worked with Android in the past, but at the implementation time, they were lazy to do it properly and they were accessing from the UI to the Rx's value.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to start my discussion as I came to this library, years ago, as an Android Developer,
Rx(n)
s work the same way thanLiveData
. This is based on a MVVM structure, but when the base for Android was to do something like (this would be done in Kotlin but I'll translate it into Dart, respecting the Android words):this way, the view of
reactiveLiveData
would be immutable from the UI, which is the base of MVVM: UI listens to reactions to the ViewModel (in our case, our GetxController).Would it be interesting to create a parent class of
Rx
andRxn
that is immutable from the UI point of view?I have been working with many developers who claimed to have worked with Android in the past, but at the implementation time, they were lazy to do it properly and they were accessing from the UI to the
Rx
's value.Beta Was this translation helpful? Give feedback.
All reactions