How primecodes-ops/crud-api works
This is a small FastAPI task-management API. A client calls the task endpoints to list and filter tasks, retrieve one task, create, update, or delete it. Request and response models describe the create/update payloads, while all task records live in a module-level in-memory list. The README documents the endpoint capabilities; the sampled implementation shows their direct access to that list. No persistent database or separate service layer is present.
Main entry points: main.py FastAPI App
Components 10
API and Status
- FastAPI App
main.py - Info and Health
main.py
Task Operations
- List and Filter
main.py - Retrieve Task
main.py - Create Task
main.py - Update Task
main.py - Delete Task
main.py
Contracts and State
- Task Models
main.py - In-Memory Tasks
main.py
Other components
- HTTP Client
Connections 14
- HTTP Client → FastAPI App: sends requests
README.md - FastAPI App → Info and Health: routes requests
main.py - FastAPI App → List and Filter: routes requests
main.py - FastAPI App → Retrieve Task: routes requests
main.py - FastAPI App → Create Task: routes requests
main.py - FastAPI App → Update Task: routes requests
main.py - FastAPI App → Delete Task: routes requests
main.py - List and Filter → In-Memory Tasks: filters and reads
main.py - Retrieve Task → In-Memory Tasks: reads
main.py - Create Task → In-Memory Tasks: appends
main.py - Update Task → In-Memory Tasks: updates
main.py - Delete Task → In-Memory Tasks: removes
main.py - Create Task → Task Models: uses payload and response
main.py - Update Task → Task Models: uses payload and response
main.py