@everystack/model 0.4.4 → 0.4.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/model",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "description": "Declare a table's schema, validation, and authorization once — compiled to migrations, RLS, and handler config",
   "license": "AGPL-3.0-only",
   "publishConfig": {

package/src/model.ts

@@ -74,6 +74,19 @@ export interface ModelDefinition {
    * is past the state — a satisfied rename is an inert notice.
    */
   renamedFrom?: string;
+  /**
+   * `movedFrom: 'old_schema'` — a one-shot migration hint, the cross-schema twin
+   * of `renamedFrom`. The SAME table name changed `schema` (e.g. `stats` → `curated`);
+   * the diff cannot distinguish a move from a CREATE-in-new-schema + an undeclared
+   * orphan left behind, so the marker carries the intent and the diff emits one
+   * `ALTER TABLE <old_schema>.<table> SET SCHEMA <schema>` (data, indexes, policies,
+   * grants, triggers and owned sequences all ride along) instead of CREATE plus a
+   * stranded copy. Names the OLD schema; the new schema is this model's `schema`.
+   * Remove it once every environment is past the state — a satisfied move is an
+   * inert notice. Cannot be combined with `renamedFrom` (declare the move first,
+   * the rename in a later increment).
+   */
+  movedFrom?: string;
   /**
    * `true` removes the table from the generic data API — `deriveHandlerConfig`
    * skips it, so it never enters `exposedTables`. Default `false`. Package-owned
@@ -111,6 +124,8 @@ export interface ModelDescriptor {
   private: boolean;
   /** One-shot rename hint: this table used to be named `renamedFrom` (same schema). */
   renamedFrom?: string;
+  /** One-shot move hint: this table used to live in schema `movedFrom` (same name) — emits SET SCHEMA. */
+  movedFrom?: string;
   /** Triggers on this table (compute — reconciled, never migrated; excluded from the base fingerprint). */
   triggers: TriggerSpec[];
   /**
@@ -161,6 +176,18 @@ export function defineModel(table: string, def: ModelDefinition): ModelDescripto
 
   validateTriggersFor('table', table, def.triggers ?? []);
 
+  // A rename and a move in one increment can't be composed from two independent markers
+  // (each names only half the source — old name OR old schema — so the diff would miss the
+  // real `old_schema.old_name` table and silently degrade to CREATE + orphan, the exact bug
+  // both markers exist to prevent). Forbid the pair; sequence them across two increments.
+  if (def.renamedFrom && def.movedFrom) {
+    throw new Error(
+      `model '${table}': cannot declare both renamedFrom ('${def.renamedFrom}') and movedFrom ('${def.movedFrom}') ` +
+        `in one increment — the diff can't locate the source. Apply the move first (movedFrom), then the rename ` +
+        `(renamedFrom) in a later increment.`,
+    );
+  }
+
   return {
     table,
     fields: def.fields,
@@ -173,6 +200,7 @@ export function defineModel(table: string, def: ModelDefinition): ModelDescripto
     schema: def.schema ?? 'public',
     private: def.private ?? false,
     ...(def.renamedFrom ? { renamedFrom: def.renamedFrom } : {}),
+    ...(def.movedFrom ? { movedFrom: def.movedFrom } : {}),
     triggers: def.triggers ?? [],
   };
 }