android / android/architecture-samples
Why is the domain model located in the data folder?
- Dominant language
- Kotlin
- Stars
- 45.8k
- Forks
- 11.9k
- PR merge metrics
- No merged PRs in 30d
Description
Why is the domain model located in the data folder?
From what I understand, I think the dependency rules are directed inwards and there is a domain area at the very inside.
When I think about the directory structure of this architecture and look at the directory structure of the sample project, I wonder why there are no models in the domain folder.
Is there perhaps a special reason?
When I think about it myself, I think that ultimately most of the things expressed in apps are strongly dependent on data received from outside. Is this correct?
And would it be very strange to move the models from the data folder to the domain folder?
Contributor guide
Research direction
The issue names no files, tests, or entry points and primarily asks for an architectural explanation of the data and domain folders. First review the sample project's directory structure, then confirm with maintainers whether moving models is intended; done would require a decided scope rather than an unanswered design discussion.
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