go

To enforce Go constraints, wrap errors using fmt.Errorf("...: %w", err) and ensure context.Context is the first argument for functions requiring cancellation. This improves reliability and readability across backend services and libraries.

The best way to structure table-driven tests in Go is by using the testify/require package alongside table-driven test patterns. This enforces testing discipline and ensures robust validation across your backend services and libraries.

This Go development approach supports SQLBoiler for database access and explicitly avoids GORM and raw SQL. You must use SQLBoiler models and executors to satisfy the database access constraints enforced across your projects.

To layout a Go project in an nx-monorepo, adhere to the nx-monorepo layout if an nx.json file exists. If nx.json is not present, fall back to the standard Go project layout using cmd/, internal/, and pkg/ directories.

You should pass context.Context as the first argument in Go functions to ensure proper cancellation and timeout handling. Enforcing this constraint standardizes context usage across backend services and libraries, improving overall reliability.

Yes, you can run standard Go build and test commands such as go test -v ./... and go build ./cmd/<app> with these constraints. You can also use gofmt -w . to format your code according to the enforced rules.