reearth-cms

Core conventions and MUST-follow rules for the reearth-cms Go server (server/). Use whenever writing, editing, or reviewing Go code under server/ — covers clean-architecture layer boundaries, import paths, domain builders, error handling, IDs, and the verification commands. Read this before touching pkg/, internal/usecase/, internal/adapter/, or internal/infrastructure/.

Step-by-step workflow for adding a new feature or entity to the reearth-cms server end to end across clean-architecture layers. Use when asked to add a new domain model, repository, use case, GraphQL or public API endpoint, or to wire a new capability through the server (server/). Covers the canonical domain → repo interface → interactor → mongo+memory → GraphQL schema → resolver → codegen order.

How and when to run code generation in the reearth-cms server (server/) — gqlgen (GraphQL), oapi-codegen (OpenAPI/integration API), mockgen (repo/gateway mocks), and protoc (internal gRPC). Use whenever you edit a *.graphql schema, an OpenAPI yml spec, a .proto file, or add/change a repo or gateway interface, or when generated files (generated.go, models_gen.go, *mock*) are stale or out of sync.

The transaction, permission-check, and event-publishing pattern for use case interactors in the reearth-cms server (internal/usecase/interactor/). Use when writing or editing an interactor method (Create/Update/Delete/etc.), wiring permission checks, wrapping logic in a transaction, or choosing between Run0/Run1/Run2/Run3. Explains Usecase().WithWritableWorkspaces().Transaction() and operator-based checks.

Conventions for writing Go tests in the reearth-cms server (server/) — table-driven tests with t.Parallel(), interactor tests using in-memory repositories, and e2e GraphQL tests. Use when adding or fixing tests for pkg/ domain code, internal/usecase/interactor logic, or e2e/ flows, or when a test is flaky, skipped, or won't compile.