@rebasepro/types 0.14.1-canary.g7e666eb → 0.14.1

package/dist/types/backend.d.ts

@@ -638,8 +638,14 @@ export interface BackendBootstrapper {
      * enum types, and never drop, narrow or rewrite anything. This runs
      * unattended against live customer data with nobody reading a diff, so the
      * destructive half stays a deliberate migration.
+     *
+     * `driverResult` is optional: this runs before `initializeDriver`, and only
+     * the bundle path has a pre-init stand-in to pass. An adapter built by an
+     * application already holds its own connection and MUST use it when this is
+     * `undefined` — dereferencing it unconditionally works for managed tenants
+     * and breaks every app that builds its own adapter.
      */
-    ensureCollectionSchema?(collections: unknown[], driverResult: InitializedDriver, log?: (message: string) => void): Promise<{
+    ensureCollectionSchema?(collections: unknown[], driverResult?: InitializedDriver, log?: (message: string) => void): Promise<{
         applied: number;
     }>;
     /**
@@ -658,7 +664,7 @@ export interface BackendBootstrapper {
      * Runs after auth initialization, because the generated policies call the
      * `auth.*` helper functions and `CREATE POLICY` validates they exist.
      */
-    ensureCollectionPolicies?(collections: unknown[], driverResult: InitializedDriver, log?: (message: string) => void): Promise<{
+    ensureCollectionPolicies?(collections: unknown[], driverResult?: InitializedDriver, log?: (message: string) => void): Promise<{
         applied: number;
     }>;
     /**

package/dist/types/database_adapter.d.ts

@@ -84,8 +84,16 @@ export interface DatabaseAdapter {
      * into a `BackendBootstrapper`: the runtime calls it through the bootstrapper
      * at boot, and a wrapper that silently omits it leaves a managed tenant
      * 500ing every data route with no create step ever having run.
+     *
+     * `driverResult` is optional because this runs BEFORE `initializeDriver`, so
+     * there may be no result to pass. The bundle path can supply a pre-init
+     * stand-in because the coordinator opened the connection itself; an app that
+     * constructed this adapter never handed the framework a connection handle,
+     * so it passes `undefined` and the adapter MUST fall back to the connection
+     * it was constructed with. An adapter that dereferences `driverResult`
+     * unconditionally works for managed tenants and breaks every self-built one.
      */
-    ensureCollectionSchema?(collections: unknown[], driverResult: InitializedDriver, log?: (message: string) => void): Promise<{
+    ensureCollectionSchema?(collections: unknown[], driverResult?: InitializedDriver, log?: (message: string) => void): Promise<{
         applied: number;
     }>;
     /**
@@ -98,7 +106,7 @@ export interface DatabaseAdapter {
      * policies, tables exist but every user-context read is denied (a public
      * collection answers 401).
      */
-    ensureCollectionPolicies?(collections: unknown[], driverResult: InitializedDriver, log?: (message: string) => void): Promise<{
+    ensureCollectionPolicies?(collections: unknown[], driverResult?: InitializedDriver, log?: (message: string) => void): Promise<{
         applied: number;
     }>;
     /**
@@ -147,4 +155,25 @@ export interface DatabaseAdapterInitConfig {
     baas?: {
         unprotectedTables?: "exclude" | "serve";
     };
+    /**
+     * What the runtime's boot-time table provisioning did, in this process,
+     * before this driver was initialized.
+     *
+     * A driver that checks for missing tables cannot otherwise tell "the create
+     * step ran and this table still is not here" from "no create step ran at
+     * all" — and those need opposite advice. The Postgres driver's drift warning
+     * assumed the first, told operators to redeploy with REBASE_MIGRATE_ON_BOOT
+     * unset, and pointed at driver version skew; for an app whose boot path had
+     * no provisioning step, all of that was unactionable and one investigation
+     * chased a driver that was perfectly current.
+     *
+     * Absent when the caller predates this field: treat that as "unknown" and
+     * fall back to generic guidance rather than asserting either case.
+     */
+    schemaProvisioning?: {
+        /** Whether the table-creation hook actually ran this boot. */
+        attempted: boolean;
+        /** Why it did not, when it did not — safe to print verbatim. */
+        reason?: string;
+    };
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@rebasepro/types",
   "type": "module",
-  "version": "0.14.1-canary.g7e666eb",
+  "version": "0.14.1",
   "description": "Rebase type definitions — shared interfaces and controller types",
   "funding": {
     "url": "https://github.com/sponsors/rebaseco"

package/src/controllers/data_driver.ts

@@ -539,6 +539,31 @@ export interface RestFetchService {
         include?: string[]
     ): Promise<Record<string, unknown>[]>;
 
+    /**
+     * `count`/`sum`/`avg`/`min`/`max` over the rows a filter selects,
+     * optionally grouped.
+     *
+     * Optional, and the REST route answers 501 where a driver does not
+     * implement it — an aggregate is not a thing to approximate, and an empty
+     * result set would read as "nothing matched".
+     *
+     * Any implementation **must apply the same row-level authorization as a
+     * read**. An aggregate is an efficient way to learn about rows you cannot
+     * select, and `count(*)` over a table whose policies would return nothing
+     * has to be zero.
+     */
+    aggregate?(
+        collectionPath: string,
+        options: {
+            aggregates: { fn: "count" | "sum" | "avg" | "min" | "max"; field?: string; alias: string }[];
+            groupBy?: string[];
+            filter?: FilterValues<string>;
+            logical?: LogicalCondition;
+            searchString?: string;
+            limit?: number;
+        }
+    ): Promise<Record<string, unknown>[]>;
+
     /**
      * Fetch a single flattened entity with optional relation includes.
      */

package/src/types/backend.ts

@@ -822,10 +822,16 @@ export interface BackendBootstrapper {
      * enum types, and never drop, narrow or rewrite anything. This runs
      * unattended against live customer data with nobody reading a diff, so the
      * destructive half stays a deliberate migration.
+     *
+     * `driverResult` is optional: this runs before `initializeDriver`, and only
+     * the bundle path has a pre-init stand-in to pass. An adapter built by an
+     * application already holds its own connection and MUST use it when this is
+     * `undefined` — dereferencing it unconditionally works for managed tenants
+     * and breaks every app that builds its own adapter.
      */
     ensureCollectionSchema?(
         collections: unknown[],
-        driverResult: InitializedDriver,
+        driverResult?: InitializedDriver,
         log?: (message: string) => void
     ): Promise<{ applied: number }>;
 
@@ -847,7 +853,7 @@ export interface BackendBootstrapper {
      */
     ensureCollectionPolicies?(
         collections: unknown[],
-        driverResult: InitializedDriver,
+        driverResult?: InitializedDriver,
         log?: (message: string) => void
     ): Promise<{ applied: number }>;
 

package/src/types/database_adapter.ts

@@ -108,10 +108,18 @@ export interface DatabaseAdapter {
      * into a `BackendBootstrapper`: the runtime calls it through the bootstrapper
      * at boot, and a wrapper that silently omits it leaves a managed tenant
      * 500ing every data route with no create step ever having run.
+     *
+     * `driverResult` is optional because this runs BEFORE `initializeDriver`, so
+     * there may be no result to pass. The bundle path can supply a pre-init
+     * stand-in because the coordinator opened the connection itself; an app that
+     * constructed this adapter never handed the framework a connection handle,
+     * so it passes `undefined` and the adapter MUST fall back to the connection
+     * it was constructed with. An adapter that dereferences `driverResult`
+     * unconditionally works for managed tenants and breaks every self-built one.
      */
     ensureCollectionSchema?(
         collections: unknown[],
-        driverResult: InitializedDriver,
+        driverResult?: InitializedDriver,
         log?: (message: string) => void,
     ): Promise<{ applied: number }>;
 
@@ -127,7 +135,7 @@ export interface DatabaseAdapter {
      */
     ensureCollectionPolicies?(
         collections: unknown[],
-        driverResult: InitializedDriver,
+        driverResult?: InitializedDriver,
         log?: (message: string) => void,
     ): Promise<{ applied: number }>;
 
@@ -178,4 +186,25 @@ export interface DatabaseAdapterInitConfig {
      * Drivers that introspect should honour `unprotectedTables`.
      */
     baas?: { unprotectedTables?: "exclude" | "serve" };
+    /**
+     * What the runtime's boot-time table provisioning did, in this process,
+     * before this driver was initialized.
+     *
+     * A driver that checks for missing tables cannot otherwise tell "the create
+     * step ran and this table still is not here" from "no create step ran at
+     * all" — and those need opposite advice. The Postgres driver's drift warning
+     * assumed the first, told operators to redeploy with REBASE_MIGRATE_ON_BOOT
+     * unset, and pointed at driver version skew; for an app whose boot path had
+     * no provisioning step, all of that was unactionable and one investigation
+     * chased a driver that was perfectly current.
+     *
+     * Absent when the caller predates this field: treat that as "unknown" and
+     * fall back to generic guidance rather than asserting either case.
+     */
+    schemaProvisioning?: {
+        /** Whether the table-creation hook actually ran this boot. */
+        attempted: boolean;
+        /** Why it did not, when it did not — safe to print verbatim. */
+        reason?: string;
+    };
 }