GetSearchContentsCountUseCase should not exist about nowinandroid HOT 2 CLOSED

I wonder why we should remove that use case rather than migrate the business logic from repository?

When we decide to use optional domain layer, move the repository's business logic to domain layer. It makes sense to me.

I read this documentation.

The reason of deleting use case is that so complicated to apply domain?

Typically, complex computations happen in the data layer to encourage reusability or caching. For example, a resource-intensive operation on a big list is better placed in the data layer than in the domain layer if the result needs to be cached to reuse it on multiple screens of the app.

And complex computations is so abstract word to me, then I am hard to decide and determine the baseline when I choose whether use domain layer or not.

In this 'Now in Android', is this GetSearchContentsCountUseCase, and getSearchContentsCount in DefaultSearchContentRepository business logic complex to use in domain?

from nowinandroid.

Following the same reasoning, what do you think about eliminating GetRecentSearchQueriesUseCase and instead allowing SearchViewModel to directly interact with the repository interface? This could simplify the architecture.

@dturner

from nowinandroid.