@bajustone/fortress 1.0.0-rc.1

package/dist/drizzle.d.cts

@@ -0,0 +1,85 @@
+import { Table } from 'drizzle-orm';
+import { D as DatabaseAdapter } from './index-CxEkfCA0.cjs';
+export { fortressPgSchema } from './drizzle/pg.cjs';
+import { AnySQLiteTable } from 'drizzle-orm/sqlite-core';
+import 'drizzle-orm/pg-core';
+
+type DrizzleDialect = 'sqlite' | 'pg';
+interface DrizzleAdapterOptions {
+    /** Override default fortress table definitions with your own Drizzle tables */
+    tables?: Partial<Record<string, Table>>;
+    /** Database dialect — controls query execution and default table definitions (default: 'sqlite') */
+    dialect?: DrizzleDialect;
+}
+/**
+ * Minimal Drizzle DB interface — accepts any Drizzle database instance.
+ * Drizzle DB types vary by dialect (BunSQLiteDatabase, PostgresJsDatabase, etc.)
+ * so we use a loose structural type rather than importing a specific one.
+ */
+interface DrizzleDB {
+    insert: Function;
+    select: Function;
+    update: Function;
+    delete: Function;
+    transaction: Function;
+}
+/**
+ * Create a DatabaseAdapter backed by any Drizzle instance.
+ * Works with PostgreSQL and SQLite (bun:sqlite, better-sqlite3).
+ *
+ * @param db - Any Drizzle database instance
+ * @param options - Optional table overrides and dialect configuration
+ */
+declare function createDrizzleAdapter(db: DrizzleDB, options?: DrizzleAdapterOptions): DatabaseAdapter;
+
+/**
+ * Database constraint-error → {@link FortressError} translation for the
+ * Drizzle adapter.
+ *
+ * Drizzle wraps driver-level errors before re-throwing, so a constraint
+ * violation typically surfaces as a generic `DrizzleQueryError` with the
+ * real driver error tucked under `error.cause`. Both matchers walk the
+ * cause chain up to a small fixed depth: {@link findSqlstate} looks for a
+ * Postgres 5-character SQLSTATE `code`, and the SQLite matcher looks for a
+ * `SQLITE_CONSTRAINT_*` code or the driver's constraint message.
+ *
+ * The mapping tables cover the constraint/concurrency states that almost
+ * every CRUD endpoint cares about. Anything not in the table is re-thrown
+ * unchanged so callers can still observe the raw driver error.
+ *
+ * {@link rethrowDbError} routes on the adapter `dialect`: Postgres via
+ * SQLSTATE, SQLite via constraint code/message. Unique violations map to
+ * `CONFLICT` (409) on both dialects so a mixed-dialect call site gets a
+ * stable wire response without branching.
+ */
+
+/**
+ * Walk the `cause` chain of an unknown thrown value looking for a property
+ * named `code` that smells like a Postgres SQLSTATE (5 uppercase
+ * alphanumerics, e.g. `23505`, `40P01`). Returns the first match it finds
+ * or `null` when none is present within {@link MAX_CAUSE_DEPTH} hops.
+ */
+declare function findSqlstate(err: unknown): string | null;
+/**
+ * Translate a driver constraint error into a {@link FortressError} for the
+ * given `dialect`, then throw it. Postgres routes through
+ * {@link PG_SQLSTATE_MAP} by SQLSTATE; SQLite through
+ * {@link SQLITE_CONSTRAINT_MAP} by constraint code/message. Errors that
+ * don't match a known constraint are re-thrown unchanged so callers can
+ * still observe the raw driver error.
+ */
+declare function rethrowDbError(err: unknown, dialect: DrizzleDialect): never;
+
+/**
+ * Aggregate of every Drizzle SQLite table fortress uses.
+ *
+ * Typed as `Record<string, AnySQLiteTable>` so JSR can statically resolve
+ * the public API without recursing through Drizzle's complex generic
+ * column types. The fortress drizzle adapter accesses tables generically,
+ * so column-level inference is not needed internally. Consumers who need
+ * column-level types should declare their own typed Drizzle schema and
+ * pass it via `createDrizzleAdapter(db, { tables })`.
+ */
+declare const fortressSchema: Record<string, AnySQLiteTable>;
+
+export { type DrizzleAdapterOptions, type DrizzleDialect, createDrizzleAdapter, findSqlstate, fortressSchema, rethrowDbError };

package/dist/drizzle.d.ts

@@ -0,0 +1,85 @@
+import { Table } from 'drizzle-orm';
+import { D as DatabaseAdapter } from './index-CxEkfCA0.js';
+export { fortressPgSchema } from './drizzle/pg.js';
+import { AnySQLiteTable } from 'drizzle-orm/sqlite-core';
+import 'drizzle-orm/pg-core';
+
+type DrizzleDialect = 'sqlite' | 'pg';
+interface DrizzleAdapterOptions {
+    /** Override default fortress table definitions with your own Drizzle tables */
+    tables?: Partial<Record<string, Table>>;
+    /** Database dialect — controls query execution and default table definitions (default: 'sqlite') */
+    dialect?: DrizzleDialect;
+}
+/**
+ * Minimal Drizzle DB interface — accepts any Drizzle database instance.
+ * Drizzle DB types vary by dialect (BunSQLiteDatabase, PostgresJsDatabase, etc.)
+ * so we use a loose structural type rather than importing a specific one.
+ */
+interface DrizzleDB {
+    insert: Function;
+    select: Function;
+    update: Function;
+    delete: Function;
+    transaction: Function;
+}
+/**
+ * Create a DatabaseAdapter backed by any Drizzle instance.
+ * Works with PostgreSQL and SQLite (bun:sqlite, better-sqlite3).
+ *
+ * @param db - Any Drizzle database instance
+ * @param options - Optional table overrides and dialect configuration
+ */
+declare function createDrizzleAdapter(db: DrizzleDB, options?: DrizzleAdapterOptions): DatabaseAdapter;
+
+/**
+ * Database constraint-error → {@link FortressError} translation for the
+ * Drizzle adapter.
+ *
+ * Drizzle wraps driver-level errors before re-throwing, so a constraint
+ * violation typically surfaces as a generic `DrizzleQueryError` with the
+ * real driver error tucked under `error.cause`. Both matchers walk the
+ * cause chain up to a small fixed depth: {@link findSqlstate} looks for a
+ * Postgres 5-character SQLSTATE `code`, and the SQLite matcher looks for a
+ * `SQLITE_CONSTRAINT_*` code or the driver's constraint message.
+ *
+ * The mapping tables cover the constraint/concurrency states that almost
+ * every CRUD endpoint cares about. Anything not in the table is re-thrown
+ * unchanged so callers can still observe the raw driver error.
+ *
+ * {@link rethrowDbError} routes on the adapter `dialect`: Postgres via
+ * SQLSTATE, SQLite via constraint code/message. Unique violations map to
+ * `CONFLICT` (409) on both dialects so a mixed-dialect call site gets a
+ * stable wire response without branching.
+ */
+
+/**
+ * Walk the `cause` chain of an unknown thrown value looking for a property
+ * named `code` that smells like a Postgres SQLSTATE (5 uppercase
+ * alphanumerics, e.g. `23505`, `40P01`). Returns the first match it finds
+ * or `null` when none is present within {@link MAX_CAUSE_DEPTH} hops.
+ */
+declare function findSqlstate(err: unknown): string | null;
+/**
+ * Translate a driver constraint error into a {@link FortressError} for the
+ * given `dialect`, then throw it. Postgres routes through
+ * {@link PG_SQLSTATE_MAP} by SQLSTATE; SQLite through
+ * {@link SQLITE_CONSTRAINT_MAP} by constraint code/message. Errors that
+ * don't match a known constraint are re-thrown unchanged so callers can
+ * still observe the raw driver error.
+ */
+declare function rethrowDbError(err: unknown, dialect: DrizzleDialect): never;
+
+/**
+ * Aggregate of every Drizzle SQLite table fortress uses.
+ *
+ * Typed as `Record<string, AnySQLiteTable>` so JSR can statically resolve
+ * the public API without recursing through Drizzle's complex generic
+ * column types. The fortress drizzle adapter accesses tables generically,
+ * so column-level inference is not needed internally. Consumers who need
+ * column-level types should declare their own typed Drizzle schema and
+ * pass it via `createDrizzleAdapter(db, { tables })`.
+ */
+declare const fortressSchema: Record<string, AnySQLiteTable>;
+
+export { type DrizzleAdapterOptions, type DrizzleDialect, createDrizzleAdapter, findSqlstate, fortressSchema, rethrowDbError };