as a constructor param. But in this case we expose android implementation and can't easily test our
ViewModel
with unit tests (without mocking the app)
a
aidanvii
05/19/2017, 8:24 AM
deviant: with
ViewModel
, I would create an wrapper of
Resources
and inject it via the constructor, perhaps provide an android implementation as a default constructor parameter, then you could mock it in tests easily.