@domain-first/project-structure 8.8.0 → 8.9.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/dist/287.js +397 -250
- package/dist/947.js +4 -0
- package/dist/agent-cli.d.ts +2 -1
- package/dist/agent-requests.d.ts +2 -0
- package/dist/graph.cjs +4 -0
- package/dist/index.cjs +401 -250
- package/dist/init.cjs +41 -37
- package/dist/integration.cjs +402 -251
- package/dist/integrations/drizzle.d.ts +8 -0
- package/dist/integrations/drizzle.spec.d.ts +1 -0
- package/dist/integrations/index.d.ts +1 -0
- package/dist/integrations/testcontainers.d.ts +1 -1
- package/dist/lint.cjs +4 -0
- package/dist/react.cjs +401 -250
- package/dist/use-cases/add-integration.d.ts +3 -3
- package/package.json +1 -1
- package/skills/df-ps-project-scripts/SKILL.md +22 -5
- package/skills/df-ps-scaffold/references/agent-operations.md +2 -1
- package/skills/df-ps-scaffold/references/generators.md +1 -1
package/README.md
CHANGED
|
@@ -116,7 +116,7 @@ System implementations are marked explicitly:
|
|
|
116
116
|
|
|
117
117
|
The first available saved type is selected by default, then an available system type; otherwise the save-entry action is selected and its name input is empty. Adding an implementation to an existing contract shows both primary and test choices. With the save action, ordinary types are remembered according to their selected environments; the run-only action never registers them.
|
|
118
118
|
|
|
119
|
-
Updates to `backend.implementations` preserve all other config sections and are saved together with generated files; cancellation discards both. Prisma
|
|
119
|
+
Updates to `backend.implementations` preserve all other config sections and are saved together with generated files; cancellation discards both. The Prisma and Drizzle integrations add `prisma` and `drizzle` to repository, command and query choices. There is no global persistence-default setting.
|
|
120
120
|
|
|
121
121
|
### How to create a bounded context
|
|
122
122
|
|
|
@@ -276,11 +276,11 @@ With Next.js, a new page also gets its App Router route, `app/admin/panel/users/
|
|
|
276
276
|
|
|
277
277
|
### How to add tooling
|
|
278
278
|
|
|
279
|
-
Run `npx df-integration` to configure one or several of the REST endpoint generator, the shared in-memory DB, Storybook, Prisma 8, Vitest, Playwright, integration tests on PostgreSQL in Testcontainers, OpenAPI generation or an Orval API client (typed client and React Query hooks). Integrations add config files, package scripts and `.gitignore` entries, then print one install command to copy. Nothing is installed or run for you.
|
|
279
|
+
Run `npx df-integration` to configure one or several of the REST endpoint generator, the shared in-memory DB, Storybook, Prisma 8, Drizzle, Vitest, Playwright, integration tests on PostgreSQL in Testcontainers, OpenAPI generation or an Orval API client (typed client and React Query hooks). Integrations add config files, package scripts and `.gitignore` entries, then print one install command to copy. Nothing is installed or run for you.
|
|
280
280
|
|
|
281
281
|
The endpoint generator and the in-memory DB are what `df-init` scaffolds; as integrations they add them later or restore missing files, and never overwrite existing ones.
|
|
282
282
|
|
|
283
|
-
With Testcontainers, the CLI asks which implementation types get integration tests (`prisma` yes, `stripe` probably not). From then on, each new implementation of such a type, like `PrismaOrdersQuery`, gets a spec in `specs/integration/` that builds it through its wire and runs against PostgreSQL in a container; an infrastructure service gets one when you ask. Unit specs stay with the domain model, services and use cases.
|
|
283
|
+
With Testcontainers, the CLI asks which implementation types get integration tests (`prisma` or `drizzle` yes, `stripe` probably not). From then on, each new implementation of such a type, like `PrismaOrdersQuery`, gets a spec in `specs/integration/` that builds it through its wire and runs against PostgreSQL in a container; an infrastructure service gets one when you ask. Unit specs stay with the domain model, services and use cases.
|
|
284
284
|
|
|
285
285
|
### How to check the rules
|
|
286
286
|
|