@u-krupaveho-kraba/form-schemas 0.2.0 → 0.3.0

package/README.md

@@ -18,16 +18,19 @@ npm install @topol/form-schemas zod
 - **Form schemas** — `FormSchema`, `StepSchema`, `FormElementSchema`, and the
   per-element-type property schemas, describing the full form JSON tree
   rendered by the Topol form widget.
-- **Campaign schemas** — `CampaignSchema`, `VariantSchema`,
-  `CampaignTargetingSchema`, `TriggerConditionSchema`, and `CampaignsFileSchema`,
-  describing a campaign's targeting rules, display trigger, and A/B variants.
+- **Campaign schemas** — `CampaignItemSchema`, `VariantSchema`,
+  `CampaignTargetingSchema`, `TriggerConditionSchema`, and
+  `CampaignItemsFileSchema`, describing one independently-evaluated
+  CampaignItem's targeting rules, display trigger, and A/B variants (there is
+  no `Campaign` wrapper -- `CampaignItem` is the atomic authored/published
+  unit, ADR 0025).
 
 ## Usage
 
 ```ts
-import { CampaignSchema } from "@topol/form-schemas";
+import { CampaignItemSchema } from "@topol/form-schemas";
 
-const result = CampaignSchema.safeParse(payload);
+const result = CampaignItemSchema.safeParse(payload);
 if (!result.success) {
   // result.error describes exactly which field failed and why
 }
@@ -40,14 +43,14 @@ Both schema families can be serialized to standard JSON Schema (draft
 feeding an LLM the exact shape of valid JSON:
 
 ```ts
-import { getFormJsonSchema, getCampaignJsonSchema } from "@topol/form-schemas";
+import { getFormJsonSchema, getCampaignItemJsonSchema } from "@topol/form-schemas";
 
 const formSchema = getFormJsonSchema();
-const campaignSchema = getCampaignJsonSchema();
+const campaignItemSchema = getCampaignItemJsonSchema();
 ```
 
-The generated Campaign JSON Schema also ships pre-built in the package at
-`schema/campaign.schema.json`, so non-TypeScript consumers (e.g. a backend
+The generated CampaignItem JSON Schema also ships pre-built in the package at
+`schema/campaignItem.schema.json`, so non-TypeScript consumers (e.g. a backend
 service in another language) can validate against the exact same contract
 without needing to run TypeScript or zod themselves.
 

package/index.js

@@ -1,6 +1,6 @@
 import * as z from "zod/mini";
 import { FormSchema } from "./schemas/form.js";
-import { CampaignSchema } from "./schemas/campaign.js";
+import { CampaignItemSchema } from "./schemas/campaign.js";
 export * from "./schemas/helpers.js";
 export * from "./schemas/formDisplay.js";
 export * from "./schemas/elementProperties.js";
@@ -16,10 +16,13 @@ export function getFormJsonSchema() {
     return z.toJSONSchema(FormSchema);
 }
 /**
- * Serializes the Campaign contract as standard JSON Schema — the artifact
- * exported to ecomailapp so its PHP publish job can validate against the
- * real schema instead of drifting silently (ticket 115/118, ADR 0017).
+ * Serializes the CampaignItem contract as standard JSON Schema — the
+ * artifact exported to ecomailapp so its PHP publish job can validate each
+ * item it builds against the real schema instead of drifting silently
+ * (ticket 115/118, ADR 0017). Renamed from `getCampaignJsonSchema` by ADR
+ * 0025: there is no `Campaign` wrapper left to serialize, `CampaignItem` is
+ * now the atomic authored/published unit.
  */
-export function getCampaignJsonSchema() {
-    return z.toJSONSchema(CampaignSchema);
+export function getCampaignItemJsonSchema() {
+    return z.toJSONSchema(CampaignItemSchema);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@u-krupaveho-kraba/form-schemas",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Zod schemas for Topol form JSON (validation gate + AI generation)",
   "author": "Topol.io",
   "license": "ISC",