new-go-endpoint

To automate generating a new Go API endpoint, provide the endpoint path, HTTP method, request and response schemas, and caching requirements. This triggers an API-first workflow that updates the OpenAPI spec, generates SQLC queries, scaffolds handlers, and applies Redis caching patterns.

The API-first workflow for adding Go backend endpoints starts by defining the API surface in an OpenAPI specification before writing code. It then automatically generates SQLC database queries, scaffolds Go handler logic, and implements Redis caching layers based on the provided schemas.

You generate SQLC queries and Redis caching by providing the new resource's endpoint path, HTTP method, and request and response schemas. The automation workflow parses these inputs to scaffold the database query layer and apply the appropriate Redis caching patterns.

This API-first endpoint generation workflow expects an existing Go backend environment configured with SQLC for SQL generation and Redis for caching. It scaffolds new handlers and queries by applying established patterns to your provided OpenAPI definitions and endpoint parameters.

To scaffold a complete Go API endpoint, you need to provide the endpoint path, HTTP method, purpose, request and response schemas, and specific caching needs. These inputs drive the automated code generation across the OpenAPI, SQLC, and Redis layers.

Yes, the workflow updates the OpenAPI spec automatically when adding new endpoints. It takes your provided path, method, and schemas, applies them to the API surface, and then proceeds to generate the corresponding SQLC queries and Go handler scaffolding.