-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about Movie vs MovieEntity #24
Comments
Movie = Domain |
Is it the case that the "entities" or "domain" layer is the innermost ring, yet data structures are suffixed with "entity" in the data layer? If so, that seems confusing. Maybe I'm misunderstanding something? |
@carterhudson "Naming is hard" )) Each layer can have its own models. |
Sure, I get that naming is hard and each layer can have its own models, but what other entities are being referred to as being part of the domain layer? I see that it includes UseCases, Entities, and Repositories, so I'm trying to find out if there's some concept I'm missing. EDIT: I did more searching and found this on the older, non-kotlin clean repo, so perhaps this answers my question. It does seem to me, however, that since the goal of this project is education, perhaps the naming conventions could be more clear? Perhaps |
IMHO, the current naming conventions is well-known in software engineering field. For example, Room uses However, I am confused by the |
I think both of those conventions are well-known in-general, but when you put it in the context of Clean and accompany it with graphics and illustrations of layers that are named differently, terms start to be conflated. |
Like stated here and detail explanation here for the difference. Solely, it's just naming but this convention make us a little easier to understand the architecture in the first impressions |
Are these models both part of the domain?
The text was updated successfully, but these errors were encountered: