Skip to content

Update language in architecture-repositories.md #1239

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

Merged
merged 1 commit into from
Aug 14, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dev/documentation/en/architecture-repositories.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ A `Repository` provides a public API to interact with an entity. The `Repository

In special cases, you may want to add, edit or delete an object without writing logs, sending emails, or updating the modified date. For example, when importing data. In such cases, you can use the [DAO](./architecture-daos) directly. In all other cases, use the `Repository` class to get, add, edit or delete objects. This will ensure that hooks, email notifications or activity logs are not skipped when an action is taken.

Think of an entity's [DAO](./architecture-daos) as a "dumb" class that only knows how to read and write data for that entity. The `Repository` is a "smart" class that coordinates that entity's relationships with other entities in the application.
An entity's [DAO](./architecture-daos) only knows how to read and write data for that entity. The `Repository` coordinates that entity's relationships with other entities in the application.

Get the `Repository` for an entity from the `Repo` facade.

Expand Down
Loading