Remove Usecases from Presentation layer
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
We should stay with the MVVM concept once we decided for it.Therefore we should find a way to remove the UI dependencies in the UseCases which are currently located in our presentation layer. They must be put into the domain layer instead:
https://github.com/owncloud/android/tree/master/owncloudApp/src/main/java/com/owncloud/android/usecases
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the use cases in owncloudApp/src/main/java/com/owncloud/android/usecases and the project's MVVM boundaries. Identify which use cases depend on the UI and what belongs in the domain layer. Done means the use cases are placed in the domain layer without UI dependencies and the presentation layer no longer owns them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100