@saasicat/adapter-prisma 1.0.0-rc.2 → 1.0.0-rc.20

package/README.md

@@ -1,5 +1,7 @@
 # @saasicat/adapter-prisma
 
+## What this is
+
 The Prisma + PostgreSQL persistence adapter for SaaSiCat. Targets the
 canonical schema from `@saasicat/spec` (`prisma-fragments/` +
 `sql/constraints.postgres.sql`) and passes the executable persistence
@@ -9,6 +11,16 @@ transaction rollback and atomic promo claims are verified, not asserted.
 > Renamed from `@saasicat/prisma` (deprecated). Same ports, superset of the
 > old exports.
 
+## What this is not
+
+Not a Prisma schema. It targets the canonical tables from `@saasicat/spec`;
+`saasicat schema apply` puts them into your `schema.prisma`, and Prisma
+migrates them. This package reads and writes them.
+
+Not a place for domain rules. An adapter translates a port to a store — which
+rows, which order, which lock — and every decision above that lives in
+`@saasicat/nest`, so the two adapters stay interchangeable.
+
 ## Quickstart — the bundle
 
 ```ts
@@ -41,10 +53,10 @@ Options:
   for schemas that differ from the 0.6 canonical layout.
 
 The bundle also ships `planCatalogReadSink` for DB hydration. To use it,
-omit `planCatalog` and pass the identity the database cannot provide:
-`SaaSiCatModule.forRoot({ persistence, dbCatalog: { projectKey,
-currency, vatRate } })` — without `dbCatalog` the module refuses to boot
-(the sink would otherwise load an empty catalog for project key `''`).
+omit `planCatalog` and name the file the settings come from:
+`SaaSiCatModule.forRoot({ persistence, dbCatalog: { path: 'config/saas.yaml' } })`
+— without `dbCatalog` the module refuses to boot, because branding, currency,
+VAT and the commercial settings cannot come from the database.
 
 Slices the mega module does not wire (promo) spread into the domain module:
 
@@ -85,6 +97,7 @@ PromoCodesModule.forRoot({
 | `PrismaMarketingSettingsRepository`      | `MarketingSettingsRepository`      | `marketing_settings`                                                |
 | `PrismaPromotionRepository`              | `PromotionRepository`              | `promotions`                                                        |
 | `PrismaSubscriptionContractRepository`   | `SubscriptionContractRepository`   | `subscription_contracts`, `contract_line_items`                     |
+| `PrismaAppliedSettingsRepository`        | `AppliedSettingsPort`              | `applied_settings`, `settings_changes`                              |
 
 Not shipped (custom adapters stay yours): registration persistence,
 consumer-specific payment/invoice integrations, and `FirstTimeCustomerCheck`.
@@ -131,10 +144,7 @@ outputs still use the semantic key:
 
 ```ts
 const schema = {
-    planBinding: {
-        mode: 'normalized-plan-id',
-        projectKey: 'my-app',
-    },
+    planBinding: { mode: 'normalized-plan-id' },
     planVersionFields: {
         validityWindows: true,
         endsAt: true,
@@ -260,3 +270,10 @@ generates a client from the composed fragments and executes the
 `@saasicat/persistence-testing` contract — CI does the same against a
 postgres service. **The database is disposable: the harness drops and
 recreates its `public` schema.**
+
+## Next
+
+- [Quickstart](../../docs/quickstart.md) — from an existing backend to an enforced feature
+- [Data model](../../docs/explanation/data-model.md) — the canonical tables, and who owns which
+- [Ports and adapters](../../docs/explanation/adr/0007-ports-and-adapters.md) — why an adapter never
+  decides

package/dist/.build-stamp

@@ -1 +1 @@
-179dbac7b9329674978a2e97b612b3514fe39b12c1bf83f6ed41a2cafc2f65bd
+a8ca1e45f5b6b53037503d71af99807b4182cce18d42b446d97a8a2b02849c87