datatug / backend / 34975033938

87%

push

github

feat(api): serve POST /v0/datatug/projects/create_project

Adds the HTTP layer and the extension config to this repo. Per sneat-go's
wire-and-configure-only rule, the api4/ext packages belong in the module's own
repo — the host only composes them.

- api4datatug: the handler runs
  apicore.VerifyAuthenticatedRequestAndDecodeBody -> facade4datatug.Facade
  .CreateProject -> apicore.ReturnJSON. The store is read from `?store=` exactly
  like the datatug CLI agent's create_project endpoint, so the web client keeps
  one call shape; a missing or unsupported store is a 400 (client error), not a
  server fault.
- datatugext.Extension(ids): the extension config the host composes. It takes
  the host's adapter for the domain's IDGenerator port, so the domain never
  learns which id library (or platform) is in use.
- api4datatug/import_pointers.go keeps the auth seam next to its shape
  declaration so the two cannot drift.

Tests drive the handler end to end against sneatcoretesting.NewMemoryDB() —
creating a project and reading both records back, an unsupported store, a
missing store, a failing ID port and an unavailable database — plus the
registered route path and the extension's identity/handler count.

93.8% statement coverage; go build / go vet / go test clean; gofmt clean.

32 of 34 new or added lines in 3 files covered. (94.12%)

88 of 96 relevant lines covered (91.67%)

0.92 hits per line