@crombolo/data 0.0.0-stage → 0.9.1

package/src/schema/change-report.ts

@@ -0,0 +1,46 @@
+/**
+ * Migration 018 — `upgrade_report` becomes `change_report`: the same stable
+ * findings shape, now shared by the pre-upgrade check and content transfer.
+ *
+ * `source` and `scope` exist because a run resolves whatever it no longer
+ * reports. Unscoped, a content check would resolve every open upgrade finding,
+ * a development boot would wipe a transfer report on every restart, and
+ * checking one bundle would resolve another's. The sweep filters on both.
+ *
+ * A rename is not expand, and the lint that says so is right in general: the
+ * rule keeps the previous release's code able to read an upgraded database.
+ * At 0.x there is no deployed node to protect and `upgrade_report` shipped in
+ * this same pre-release line, so the exception is taken deliberately here and
+ * comes off at 1.0.
+ */
+import type { Db } from '../database.ts'
+import type { Migration } from '../migrations.ts'
+import { schemaOps } from '../schema-ops.ts'
+import { STATE_ASSISTANT } from './assistant.ts'
+
+export const STATE_CHANGE_REPORT = '{6f1d4a8e-0018-4a3f-9c62-7d5b1e8a3c92}'
+
+export const changeReportMigration: Migration = {
+  from: STATE_ASSISTANT,
+  to: STATE_CHANGE_REPORT,
+  name: 'RenameUpgradeReportToChangeReport',
+  kind: 'expand',
+  release: '0.3.0',
+  async up(db: Db) {
+    const t = db.dialect.types
+    const ops = schemaOps(db)
+    await ops.renameTable('upgrade_report', 'change_report')
+    // Both dialects keep an index across a table rename, under its old name.
+    await ops.dropIndex('ix_upgrade_report_subject', 'change_report')
+    await ops.addColumn('change_report', 'source', `${t.varchar(20)} NOT NULL DEFAULT 'upgrade'`)
+    await ops.addColumn('change_report', 'scope', t.varchar(64))
+    await ops.addIndex('ix_change_report_subject', 'change_report', [
+      'source',
+      'scope',
+      'code',
+      'subject_key',
+      'property_alias',
+      'culture',
+    ])
+  },
+}

package/src/schema/client-id-prefix.ts

@@ -0,0 +1,43 @@
+/**
+ * Migration 020 — API-user client IDs carry crombolo's own prefix.
+ *
+ * The prefix exists so an API user's client ID cannot collide with the
+ * backoffice client's own, which is `umbraco-back-office` and is not ours to
+ * rename: the vendored client sends it on every authorize call. The API-user
+ * prefix *is* ours, and it put Umbraco's name on a string administrators type
+ * and paste into their own integration config.
+ *
+ * Only the ID moves. `secret_hash` is untouched, so an existing credential
+ * keeps working once the caller sends the new ID — no secret has to be
+ * re-issued.
+ *
+ * The two prefixes are spelled out rather than imported. A migration has to
+ * describe what it did on the day it ran, and a constant someone later edits
+ * would quietly rewrite history.
+ */
+import type { Db } from '../database.ts'
+import type { Migration } from '../migrations.ts'
+import { STATE_TRANSFER_RUNS } from './transfer-runs.ts'
+
+export const STATE_CLIENT_ID_PREFIX = '{6f1d4a8e-0020-4b7d-8e41-6c2a9f3d5e84}'
+
+const OLD_PREFIX = 'umbraco-back-office-'
+const NEW_PREFIX = 'crombolo-back-office-'
+
+export const clientIdPrefixMigration: Migration = {
+  from: STATE_TRANSFER_RUNS,
+  to: STATE_CLIENT_ID_PREFIX,
+  name: 'RenameClientIdPrefix',
+  kind: 'expand',
+  release: '0.3.0',
+  async up(db: Db) {
+    // `client_id` is the primary key and nothing references it, so this is an
+    // update in place. SUBSTR is 1-based in both dialects.
+    await db.exec(
+      `UPDATE user_client_credential
+          SET client_id = ? || SUBSTR(client_id, ?)
+        WHERE client_id LIKE ?`,
+      [NEW_PREFIX, OLD_PREFIX.length + 1, `${OLD_PREFIX}%`],
+    )
+  },
+}

package/src/schema/content-editing.ts

@@ -0,0 +1,50 @@
+/**
+ * Migration 010 — what the document action menu stores beyond versions:
+ * scheduled publishing (Umbraco's `umbracoContentSchedule`), per-user
+ * notification subscriptions (`umbracoUser2NodeNotify`) and culture and
+ * hostnames (`umbracoDomain`), snake-cased.
+ */
+import type { Db } from '../database.ts'
+import type { Migration } from '../migrations.ts'
+import { STATE_RICH_TEXT_UI } from './rich-text-ui.ts'
+
+export const STATE_CONTENT_EDITING = '{6f1d4a8e-0010-4c21-9d3a-8b1e5c7a2f10}'
+
+export const contentEditingMigration: Migration = {
+  from: STATE_RICH_TEXT_UI,
+  to: STATE_CONTENT_EDITING,
+  name: 'AddContentEditingTables',
+  kind: 'expand',
+  release: '0.3.0',
+  async up(db: Db) {
+    const t = db.dialect.types
+    await db.exec(
+      `CREATE TABLE content_schedule (
+         id ${t.identity},
+         node_id ${t.integer} NOT NULL REFERENCES node (id),
+         language_id ${t.integer} NULL REFERENCES language (id),
+         action ${t.varchar(16)} NOT NULL,
+         date ${t.timestamp} NOT NULL
+       )`,
+    )
+    await db.exec('CREATE INDEX ix_content_schedule_date ON content_schedule (date)')
+    await db.exec(
+      `CREATE TABLE user_notification (
+         user_id ${t.integer} NOT NULL REFERENCES user_account (id),
+         node_id ${t.integer} NOT NULL REFERENCES node (id),
+         action ${t.varchar(64)} NOT NULL,
+         PRIMARY KEY (user_id, node_id, action)
+       )`,
+    )
+    await db.exec(
+      `CREATE TABLE domain (
+         id ${t.identity},
+         node_id ${t.integer} NOT NULL REFERENCES node (id),
+         language_id ${t.integer} NULL REFERENCES language (id),
+         domain_name ${t.textCi} NOT NULL,
+         sort_order ${t.integer} NOT NULL
+       )`,
+    )
+    await db.exec('CREATE UNIQUE INDEX ix_domain_name ON domain (domain_name)')
+  },
+}