Both of these events exist under MvpApiService and should probably be handled accordingly. However, currently, the MvpApiService is being injected into the viewmodels through the constructor. Wiring up additional events there feels... smelly.
Would love to figure out a better approach to this.
Both of these events exist under
MvpApiService
and should probably be handled accordingly. However, currently, theMvpApiService
is being injected into the viewmodels through the constructor. Wiring up additional events there feels... smelly.Would love to figure out a better approach to this.