Skip to content

Commit df66e7f

Browse files
committed
linting fixes
Signed-off-by: bidi <bidi@apidemia.com>
1 parent 26178ff commit df66e7f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/book/v7/introduction/architecture-at-a-glance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Here's how a typical request flows through Dotkernel API:
9595
|-------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------|
9696
| Handlers (PSR-15) | Process incoming HTTP requests, coordinate application logic/services, and return the HTTP response | `GetUserResourceHandler.php`, `PostUserResourceHandler.php` | Some of the benefits are: separation of concerns, easier testing, clearer intent |
9797
| Services | Contains the business logic layer that sits between the handlers and repositories | Business rules validation, Data transformation, Cross-cutting concerns | Execution flow: `Handler → Service → Repository → Database` |
98-
| Repositories | Data access layer using Doctrine ORM | Query building, Entity persistence, Database abstraction | The only component that interacts with the database |
98+
| Repositories | Data access layer using Doctrine ORM | Query building, Entity persistence, Database abstraction | The only component that interacts with the database |
9999
| Input Filters | Filter and validate requests using Laminas InputFilter | Login form, contact us form, `$_GET` and `$_POST` values, CLI arguments | Execution flow: `Request → InputFilter → Validation → Handler` |
100100
| Entities | Represent database tables using Doctrine ORM | `class User { ... }` | Ensure consistency between database and application data |
101101

0 commit comments

Comments
 (0)