Question about Movie vs MovieEntity about android-cleanarchitecture-kotlin HOT 7 CLOSED

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 MovieEntity could be MovieData denoting the data layer, the domain could have the canonical Movie or MovieEntity and the presentation layer could be MovieView? I'm just spitballing, but I'm trying to advocate for adopting clean and I'd like to head off any confusion if and when I have to explain these concepts to others.

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

from android-cleanarchitecture-kotlin.

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 MovieEntity could be MovieData denoting the data layer, the domain could have the canonical Movie or MovieEntity and the presentation layer could be MovieView? I'm just spitballing, but I'm trying to advocate for adopting clean and I'd like to head off any confusion if and when I have to explain these concepts to others.

from android-cleanarchitecture-kotlin.

Movie = Domain
MovieEntity = DataLayer

from android-cleanarchitecture-kotlin.

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?

from android-cleanarchitecture-kotlin.

@carterhudson "Naming is hard" ))

Each layer can have its own models.

from android-cleanarchitecture-kotlin.

IMHO, the current naming conventions is well-known in software engineering field. For example, Room uses Entity annotation to annotate a class as a db entity.

However, I am confused by the MovieView, it makes me think it is an android View but a model in presentation layer.

from android-cleanarchitecture-kotlin.

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.

from android-cleanarchitecture-kotlin.