How pedrogagodev/dailydietapi works
Project type and purpose
• This is a full-stack diet-tracking application:
• Backend: A RESTful API (“DailyDietAPI”) built with Node.js, Fastify and TypeScript, following Clean Architecture.
• Frontend: A React/TypeScript web app using Vite, providing UI for registration, login, meal CRUD and metrics dashboard.
• Purpose: Let users register/login, record meals (with diet compliance flag), view metrics (total, on/off diet counts, best streak).
File structure
• Top-level “backend” and “frontend” directories indicate clear separation.
• Backend follows Clean Architecture:
• src/core (entities, repositories interfaces)
• src/use-cases (business logic)
• src/infra (database connection)
• src/repositories (concrete adapters)
• src/http (controllers, routes, middlewares)
• Database migrations under backend/database.
• Automated tests in controllers and use-cases.
• Frontend contains:
• components, pages, layouts, hooks, contexts
• services (httpClient, authService, mealsService)
• types and utils.
• Configuration: tsconfig, biome.json, Docker Compose for local Postgres.
Key README insights
• Architecture: Clean Architecture, separation of concerns.
• Tech stack: Node.js, Fastify, TypeScript, PostgreSQL, React/Vite.
• Security: JWT authentication, user isolation.
• Non-functional: performance, maintainability, test coverage.
Detail
• Middleware between HTTP server and controllers.
• Schema validation step (zod) before controller logic.