docs(guides): scaffolding-a-feature notes conformance-ready output
This commit is contained in:
@@ -32,6 +32,17 @@ pnpm install # link the new workspace package
|
||||
pnpm --filter @repo/widgets lint typecheck test
|
||||
```
|
||||
|
||||
## Conformance-ready by default
|
||||
|
||||
Since milestone v of the conformance system, `pnpm turbo gen feature <name>` emits two conformance artefacts:
|
||||
|
||||
- **`src/feature.manifest.ts`** declaring the scaffolded `getX` use case
|
||||
- **`src/di/bind-production.ts`** with `assertFeatureConformance(...)` called at the tail
|
||||
|
||||
Run `pnpm conformance` after generating a feature — it should pass cleanly. If you add `bus.publish("X")` calls in a factory body, you'll also need to add `"X"` to the manifest's `publishes[]` array for that use case, or the `no-undeclared-event-publish` ESLint rule will warn.
|
||||
|
||||
See `docs/guides/conformance-quickref.md` for the manifest field reference.
|
||||
|
||||
## What it generates
|
||||
|
||||
- Package files: `package.json`, `tsconfig.json`, `vitest.config.ts`,
|
||||
|
||||
Reference in New Issue
Block a user