reservations-service

To add a new Fastify route, define the endpoint schema under `src/schemas`, implement the business logic in `src/services` using Prisma models, apply `requireAuth` or `optionalAuth`, and add Vitest coverage to validate response status codes and payloads.

You can test Fastify reservation endpoints with Vitest by writing mocked route tests that mock the Prisma service layer and Auth0 JWT verification behavior, allowing you to validate expected HTTP status codes and response payload shapes without hitting the database.

Handling Auth0 JWT authentication in a table management API requires using `requireAuth` for protected reservation operations and `optionalAuth` for endpoints like availability checks, ensuring Fastify route schemas enforce the correct access levels based on the endpoint's purpose.

Yes, you must update the OpenAPI schema under `src/schemas` when adding new reservation or table management endpoints to ensure the API documentation reflects the new Fastify routes, request parameters, and response payload structures accurately.

Yes, you can use Prisma to manage table holds and cancellations by implementing the business logic within `src/services/reservation.ts` or `src/services/table.ts`, manipulating the `Table` and `Reservation` models according to your existing Fastify route structure patterns.

Mocked Vitest tests for reservation routes often fail when the mock service layer does not match the exact Prisma model responses expected by the logic in `src/services`, or if the Auth0 JWT verification behavior is not properly mocked alongside the Fastify route schemas.