kanbo-cli 0.1.0

package/dist/lib/postgres/index.mjs

@@ -0,0 +1,35 @@
+import { r as BOARD_SCHEMA_EPOCH } from "../migrations-path-Ciwan537.mjs";
+import { _ as issueStatuses, a as BOARD_REFUSAL_ERRCODE, c as getBoardMigrationsPath, d as boardPostgresSchema, f as issueComments, g as issueRuns, h as issueRelations, i as BOARD_PERSON_ROLE, l as createPostgresBoardStore, m as issueMilestones, n as AGENT_WAITING_REFUSAL, o as BOARD_ROLE_SQL, p as issueFieldChanges, r as BOARD_AGENT_ROLE, s as assertBoardSchema, t as AGENT_APPROVAL_COMMENT_REFUSAL, u as BOARD_POSTGRES_TABLES, v as issues, y as kanbanMeta } from "../roles.sql-CvyCGt38.mjs";
+import { entityKind } from "drizzle-orm";
+import { migrate } from "drizzle-orm/postgres-js/migrator";
+import { migrate as migrate$1 } from "drizzle-orm/pglite/migrator";
+//#region src/postgres/migrate.ts
+/**
+* Bring an external board database up to the schema this build speaks.
+*
+* Unlike a host app's database — whose schema the app migrates itself — an
+* external database has no owner but this package, so this
+* is the one place that creates or updates it. Drizzle records what it applied
+* in `__drizzle_migrations`, which is what makes a second run a no-op.
+*/
+async function migrateBoardDatabase(database) {
+	const config = { migrationsFolder: getBoardMigrationsPath() };
+	if (isPgliteDatabase(database)) {
+		await migrate$1(database, config);
+		return;
+	}
+	await migrate(database, config);
+}
+/**
+* Which driver is underneath. Drizzle stamps every one of its classes with a
+* name for exactly this question, and asking it keeps the embedded Postgres out
+* of the packaged command: importing the pglite *driver* to test against would
+* pull the WebAssembly build in with it, while its migrator carries nothing.
+*/
+function isPgliteDatabase(database) {
+	return database.constructor[entityKind] === "PgliteDatabase";
+}
+//#endregion
+export { AGENT_APPROVAL_COMMENT_REFUSAL, AGENT_WAITING_REFUSAL, BOARD_AGENT_ROLE, BOARD_PERSON_ROLE, BOARD_POSTGRES_TABLES, BOARD_REFUSAL_ERRCODE, BOARD_ROLE_SQL, BOARD_SCHEMA_EPOCH, assertBoardSchema, boardPostgresSchema, createPostgresBoardStore, getBoardMigrationsPath, issueComments, issueFieldChanges, issueMilestones, issueRelations, issueRuns, issueStatuses, issues, kanbanMeta, migrateBoardDatabase };
+
+//# sourceMappingURL=index.mjs.map

package/dist/lib/postgres/index.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.mjs","names":["migratePgliteDatabase","migratePostgresJsDatabase"],"sources":["../../../src/postgres/migrate.ts"],"sourcesContent":["import { entityKind } from 'drizzle-orm'\nimport type { PgliteDatabase } from 'drizzle-orm/pglite'\nimport { migrate as migratePgliteDatabase } from 'drizzle-orm/pglite/migrator'\nimport type { PostgresJsDatabase } from 'drizzle-orm/postgres-js'\nimport { migrate as migratePostgresJsDatabase } from 'drizzle-orm/postgres-js/migrator'\n\nimport { getBoardMigrationsPath } from './migrations-path'\n\n/**\n * A Postgres board this package can migrate: the driver an app and the command\n * line connect with, and the embedded one the tests run on. Drizzle ships a\n * migrator per driver, so both are named here rather than one abstract\n * `PgDatabase` — the drivers differ in their result type, and nothing else.\n */\nexport type MigratablePostgresDatabase<TSchema extends Record<string, unknown> = Record<string, never>>\n  = PgliteDatabase<TSchema> | PostgresJsDatabase<TSchema>\n\n/**\n * Bring an external board database up to the schema this build speaks.\n *\n * Unlike a host app's database — whose schema the app migrates itself — an\n * external database has no owner but this package, so this\n * is the one place that creates or updates it. Drizzle records what it applied\n * in `__drizzle_migrations`, which is what makes a second run a no-op.\n */\nexport async function migrateBoardDatabase<TSchema extends Record<string, unknown>>(\n  database: MigratablePostgresDatabase<TSchema>,\n): Promise<void> {\n  const config = { migrationsFolder: getBoardMigrationsPath() }\n  if (isPgliteDatabase(database)) {\n    await migratePgliteDatabase(database, config)\n    return\n  }\n  await migratePostgresJsDatabase(database, config)\n}\n\n/**\n * Which driver is underneath. Drizzle stamps every one of its classes with a\n * name for exactly this question, and asking it keeps the embedded Postgres out\n * of the packaged command: importing the pglite *driver* to test against would\n * pull the WebAssembly build in with it, while its migrator carries nothing.\n */\nfunction isPgliteDatabase<TSchema extends Record<string, unknown>>(\n  database: MigratablePostgresDatabase<TSchema>,\n): database is PgliteDatabase<TSchema> {\n  return (database.constructor as { [entityKind]?: string })[entityKind] === 'PgliteDatabase'\n}\n"],"mappings":";;;;;;;;;;;;;;AAyBA,eAAsB,qBACpB,UACe;CACf,MAAM,SAAS,EAAE,kBAAkB,uBAAuB,EAAE;CAC5D,IAAI,iBAAiB,QAAQ,GAAG;EAC9B,MAAMA,UAAsB,UAAU,MAAM;EAC5C;CACF;CACA,MAAMC,QAA0B,UAAU,MAAM;AAClD;;;;;;;AAQA,SAAS,iBACP,UACqC;CACrC,OAAQ,SAAS,YAA0C,gBAAgB;AAC7E"}