nextcloud / nextcloud/talk-android
Make use of DomainsLayers/UseCases
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
As the app grows and calls to repositories are needed in multiple places, it makes sense to make use of "UseCases" to avoid redundant code.
Explanation at
https://medium.com/@ami0275/mvvm-clean-architecture-pattern-in-android-with-use-cases-eff7edc2ef76
As an example where this would make sense look at this comment: https://github.com/nextcloud/talk-android/pull/4333/files#r1810614023
As soon as a some UseCases have been implemented, this issue can be closed and the implementations should serve as a example.
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 reading the linked Clean Architecture explanation and the referenced comment in pull request #4333. Identify repository calls that are repeated across the app and define a small set of representative UseCases; the issue is done when those examples are implemented and can guide further work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100