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
Some frameworks in the domain are actually not being used in the use cases. We should remove them and put those interfaces in the framework modules instead.
The text was updated successfully, but these errors were encountered:
Only put Android Frameworks in the domain especially their interfaces if it's actually crucial or needed in use cases. I've been wrapping my head around before on how to make wrappers from those Android Classes without realizing that they're actually useless in the domain.
The best use case example is UpdateUsageStatsForegroundServiceUseCase.kt where it actually use an Android Framework called UsageStatsManager which is only for Android so it should be included in the domain as framework.
Some frameworks in the domain are actually not being used in the use cases. We should remove them and put those interfaces in the framework modules instead.
The text was updated successfully, but these errors were encountered: