-
Notifications
You must be signed in to change notification settings - Fork 45
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
Fix FavoritesViewModel implementation #62
Comments
JoaquimLey
added a commit
that referenced
this issue
Sep 25, 2018
Continue migrating the FavoritesViewModel implementation for the UseCase interactors - Will create a Transport repository that takes the SMSController - Handles the request and sends back the response. #62
JoaquimLey
added a commit
that referenced
this issue
Sep 25, 2018
- Simplified the way how FlowableUseCases are executed - Removed a need of a specific Subscriber, and let consumer handle that - Was wrongly building the useCases instead of executing in the FavVMImpl - Renamed ui layer model to TransportUiModel (was FavoriteViewObject) *UiModel will represent the viewState. #62
JoaquimLey
added a commit
that referenced
this issue
Sep 25, 2018
JoaquimLey
added a commit
that referenced
this issue
Sep 25, 2018
- More tests related to favoritesViewmodel with use cases. #62
JoaquimLey
added a commit
that referenced
this issue
Sep 26, 2018
JoaquimLey
added a commit
that referenced
this issue
Sep 26, 2018
JoaquimLey
added a commit
that referenced
this issue
Sep 29, 2018
Merged
Closing as handling the remaining use-cases will make more sense when there's a decision (will open a new issue). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the introduction of the
Domain
layer, the current implementation makes no sense (directly leakingSmsController
)Remove all of the
SmsController
related codeHandle (and execute) UseCases
Fix Unit tests
The text was updated successfully, but these errors were encountered: