Purpose of Entities about course-project-aarves

[lanthony42]

Basically, we need to nail down the flow of data / control in our application.

[rebplane]

"Are entities basically just in-memory data storage for convenience more than anything?"
Pretty much, yes.

The way I see it, the entities are mapped onto the database (each entity is stored in the database, the database only contains the attributes of the entity, so it's pretty much a one-to-one mapping).

On program startup, the data is loaded to entities to be able to modify them and use them (otherwise we would always need to go back to the database class through a gateway and sift through the information for what we need, rather than what we have now - controller -> use case -> entity to just grab what information we need/modify it).

DTO (if I understand it correctly) is an object that carries/transfer the data between processes - it does not have any uses other than simply serialization and deserialization. In comparison to entities, they do not contain any business logic.

"Basically, we need to nail down the flow of data / control in our application."

I agree though. We'll use the other issue to discuss further on data transfer. We also need to figure out how we are presenting the data as well (which UI design pattern - MVP, MVC, MVVM? Are we doing this already?).

[lanthony42]

We should have another issue for sorting out UI Clean Architecture

[lanthony42]

The main issue is trying to differentiate DTOs and entities in our code to justify their (DTOs) existence as not just repeated code. Meaning, what exactly should our entities have in terms of "business logic"? Right now it seems a bit sparse.

[rebplane]

We have the entities ReviewList and AccountList, the databases accounts.json, reviews.json.

Just to clarify, what are the DTOs in our code right now, or have we yet to add them into our code?

[lanthony42]

We need to add them so that our code adheres to Clean Architecture.

[lanthony42]

Discussion moved to #43.