- Add consent to CORE_PACKAGE_GENERATORS in turbo/generators/config.ts so pnpm turbo gen core-package consent is a valid command (not hand-rollable) - Create turbo/generators/templates/core-package/consent/ mirroring the analytics template shape (AGENTS.md, package.json, tsconfig, turbo, vitest, eslint, src/index.ts scaffolds) - Regenerate packages/core-consent/ from the new template (replaces the previous hand-rolled attempt that violated the generator-first rule) - Add __consentChecked to withCapture PROPAGATED_BRANDS so the brand bubbles through the full withSpan→withCapture wrapper chain to the outermost binding that assertFeatureConformance reads Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
@repo/core-consent
Optional core package providing a vendor-neutral consent management interface. Scaffold via pnpm turbo gen core-package consent.
Structure
src/
consent-types.ts # ConsentCategory, ConsentState, UserConsentState
consent.interface.ts # IConsent — isGranted, grant, withdraw, getCategories
with-consent.ts # withConsent wrapper attaching ConsentChecked brand
index.ts # Barrel export
Design
IConsent exposes four methods:
isGranted(category)— synchronous check whether consent is grantedgrant(category)— record consent grant for a categorywithdraw(category)— record consent withdrawal for a categorygetCategories()— list all known consent states
The interface is vendor-neutral: no storage implementation is bundled here. Concrete implementations (e.g. a Payload-backed store) are wired at DI bind time in bind-production.
withConsent wraps a use-case factory at bind time, attaches the __consentChecked brand, and is the innermost wrapper in the composition chain:
withSpan → withCapture → withAudit → withAnalytics → withConsent → factory(deps)
See docs/architecture/agent-first-workflow-and-conformance.md for the dependency-injection conventions.