Skip to content
Merged
Show file tree
Hide file tree
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
13 changes: 13 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Ignore build outputs
bin/
obj/
*.user
*.db
*.db-shm
*.db-wal
Todo.Tests/bin/
Todo.Tests/obj/
# Ignore VS folder
.vs/
# ignore local environment files
app.db*
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,3 +29,6 @@ git clone https://github.com/Romulo-Queiroz/todoListFront
| :-------------------------------------------------------------------------------------------------------------------------------------: |

</div>

## Architecture Diagram
See [docs/architecture.md](docs/architecture.md) for a high level flow of how the API handles requests.
22 changes: 22 additions & 0 deletions docs/architecture.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Project Flow

The diagram below summarizes how requests are processed in the Task Manager API.

```mermaid
flowchart TD
Client((Client)) -->|HTTP request| Controller[Controllers]
Controller --> Service[Services]
Service --> Dal[DAL]
Dal --> Db[(Database)]
Service -->|Returns data| Controller
Controller -->|JSON| Client
```

Each layer has a specific responsibility:

- **Controllers** handle HTTP requests and responses.
- **Services** contain business logic.
- **DAL (Data Access Layer)** interacts with the database via Entity Framework Core.
- **Database** stores tasks, categories, and users.

Use this diagram to explain the flow of information through the application.
Loading