@rebasepro/types 0.9.1-canary.f0ac103 → 0.9.1-canary.fd3754b

package/dist/controllers/data.d.ts

@@ -149,15 +149,6 @@ export interface CollectionAccessor<M extends Record<string, unknown> = Record<s
      * @returns The created entity
      */
     create(data: Partial<EntityValues<M>>, id?: string | number): Promise<Entity<M>>;
-    /**
-     * Create many records in a single transaction.
-     *
-     * See {@link SDKCollectionClient.createMany}. Optional: not every driver can
-     * write in bulk, and callers should fall back to `create` per record.
-     */
-    createMany?(data: Partial<EntityValues<M>>[], options?: {
-        upsert?: boolean;
-    }): Promise<Entity<M>[]>;
     /**
      * Update an existing record by ID.
      * @returns The updated entity
@@ -271,43 +262,10 @@ export interface SDKCollectionClient<M extends Record<string, unknown> = Record<
     /**
      * Create a new record.
      * @param data The record data to create (the collection's `Insert` shape).
-     * @param id Optional specific id, sent as an `id` column. This is for tables
-     *   whose key *is* `id`: the value goes in as that column. For a table keyed
-     *   on anything else (a `sku`, a composite key), there is no `id` column to
-     *   receive it — put the key in `data` instead, where it belongs among the
-     *   columns.
+     * @param id Optional specific ID to use for the new record.
      * @returns The created row
      */
     create(data: I, id?: string | number): Promise<M>;
-    /**
-     * Write many records in a single request and a single transaction.
-     *
-     * Built for imports and ETL, where one call per row means one HTTP round
-     * trip and one transaction per row. Every record still runs the normal
-     * pipeline — callbacks, relations, row-level security — and the batch is
-     * all-or-nothing: if any record is rejected, none of them land and the
-     * error names the offending index.
-     *
-     * A record carrying its primary key updates that row; one without inserts.
-     * With `{ upsert: true }` each record is written as INSERT ... ON CONFLICT
-     * DO UPDATE on the primary key instead, which is what makes a re-runnable
-     * import idempotent.
-     *
-     * Batches are capped server-side (1000 rows by default) because one batch
-     * holds its locks for the whole transaction — chunk larger jobs.
-     *
-     * @returns The written rows, in the order given.
-     *
-     * @example
-     * ```ts
-     * for (const chunk of chunks(rows, 1000)) {
-     *     await client.data.products.createMany(chunk, { upsert: true });
-     * }
-     * ```
-     */
-    createMany(data: I[], options?: {
-        upsert?: boolean;
-    }): Promise<M[]>;
     /**
      * Update an existing record by ID.
      * @param data The fields to update (the collection's `Update` shape).
@@ -387,7 +345,7 @@ export type RebaseData<DB = unknown> = {
  * - The frontend SDK client (`client.data.products.find()`)
  * - Backend framework callbacks & scripts (`context.data.products.find()`)
  *
- * Every accessor returns flat rows (the table's columns) via
+ * Every accessor returns flat rows (`{ id, ...columns }`) via
  * {@link SDKCollectionClient} — access fields directly (`row.title`), never
  * `row.values.title`. The admin CMS uses {@link RebaseData} (Entity) instead.
  *

package/dist/controllers/data_driver.d.ts

@@ -65,30 +65,6 @@ export interface SaveProps<M extends Record<string, unknown> = Record<string, un
     previousValues?: Partial<EntityValues<M>>;
     collection?: CollectionConfig<M>;
     status: EntityStatus;
-    /**
-     * Write the row with INSERT ... ON CONFLICT DO UPDATE on the primary key
-     * instead of choosing between insert and update up front.
-     *
-     * One statement, so it does not lose the race a read-then-write can, and it
-     * succeeds whether or not the row is already there — what a re-runnable
-     * import needs. Requires every primary key column to be present; without
-     * them there is no conflict target and the row is inserted normally.
-     */
-    upsert?: boolean;
-}
-/**
- * @internal
- */
-export interface SaveManyProps<M extends Record<string, unknown> = Record<string, unknown>> {
-    path: string;
-    /**
-     * The rows to write. A row carrying its primary key updates (or, with
-     * `upsert`, inserts-or-updates) that row; one without inserts.
-     */
-    rows: Partial<EntityValues<M>>[];
-    collection?: CollectionConfig<M>;
-    /** Apply every row as INSERT ... ON CONFLICT DO UPDATE. See {@link SaveProps.upsert}. */
-    upsert?: boolean;
 }
 /**
  * @internal
@@ -159,19 +135,6 @@ export interface DataDriver {
      * @param props
      */
     save<M extends Record<string, unknown> = Record<string, unknown>>(props: SaveProps<M>): Promise<Record<string, unknown>>;
-    /**
-     * Save many rows as one unit of work.
-     *
-     * Every row runs the same pipeline as {@link save} — callbacks, relations
-     * and row-level security all still apply — but they share a single
-     * transaction, so the batch either lands whole or not at all. That, and the
-     * single round trip, is what makes importing tens of thousands of rows
-     * viable without dropping to raw SQL.
-     *
-     * Optional: drivers that cannot do this leave it undefined and callers fall
-     * back to `save` per row.
-     */
-    saveMany?<M extends Record<string, unknown> = Record<string, unknown>>(props: SaveManyProps<M>): Promise<Record<string, unknown>[]>;
     /**
      * Delete a entity
      * @param props
@@ -240,14 +203,9 @@ export interface DataDriver {
  * REST-optimised fetch service exposed by drivers that support
  * eager-loading of relations via `include`.
  *
- * The methods return flattened rows — exactly the table's columns, under their
- * own names and with the types the database returned — and included relations
- * inlined as plain nested rows. This is the shape served to app developers
- * through the REST API / SDK client.
- *
- * No synthesized `id`: identity is a primary key, which may be named anything
- * and span several columns, so an address is derived by whoever needs one (see
- * `buildCompositeId`) rather than written into the row on top of the data.
+ * The methods return flattened rows (`{ id, ...columns }`) with
+ * included relations inlined as plain nested rows — the shape served
+ * to app developers through the REST API / SDK client.
  *
  * @group DataDriver
  */

package/dist/index.es.js

@@ -312,23 +312,6 @@ function getDeclaredSubcollections(collection) {
 }
 //#endregion
 //#region src/types/policy.ts
-/**
-* The id a request without a logged-in user reports as `auth.uid()`.
-*
-* A user-context request always sets `app.user_id`: blank would read back as
-* `NULL`, and `NULL` is how the trusted server context is recognised, so an
-* anonymous visitor would be promoted to server privileges. The driver
-* therefore substitutes this sentinel at the single chokepoint where the GUC
-* is set.
-*
-* The consequence for policy authors is that **`auth.uid() IS NOT NULL` is a
-* tautology on the user path** — it is true for anonymous visitors too. Use
-* {@link policy.authenticated} (or `auth.uid() <> 'anonymous'`) to mean "signed
-* in", and {@link policy.serverContext} to mean "the trusted server context".
-*
-* @group Models
-*/
-var ANONYMOUS_USER_ID = "anonymous";
 /** @group Models */
 var policy = {
 	true: () => ({ kind: "true" }),
@@ -360,7 +343,6 @@ var policy = {
 		roles
 	}),
 	authenticated: () => ({ kind: "authenticated" }),
-	serverContext: () => ({ kind: "serverContext" }),
 	existsIn: (args) => ({
 		kind: "existsIn",
 		collection: args.collection,
@@ -568,6 +550,6 @@ function isPublicStoragePath(path) {
 	return p.startsWith("public/") || p.startsWith(`default/public/`);
 }
 //#endregion
-export { ALL_WHERE_FILTER_OPS, ANONYMOUS_USER_ID, CANONICAL_TO_REST, DEFAULT_CAPABILITIES, DEFAULT_DATA_SOURCE_KEY, DEFAULT_STORAGE_SOURCE_KEY, EntityReference, EntityRelation, FIREBASE_CAPABILITIES, GeoPoint, MONGODB_CAPABILITIES, NULL_OPS, POSTGRES_CAPABILITIES, PUBLIC_STORAGE_PREFIX, REST_TO_CANONICAL, RebaseApiError, RebaseClientError, Vector, getCollectionDataPath, getDataSourceCapabilities, getDeclaredSubcollections, isBranchAdmin, isDocumentAdmin, isFirebaseCollectionConfig, isLazyComponentRef, isMongoDBCollectionConfig, isPostgresCollectionConfig, isPublicStoragePath, isSQLAdmin, isSchemaAdmin, policy, registerDataSourceCapabilities, toCanonicalOp };
+export { ALL_WHERE_FILTER_OPS, CANONICAL_TO_REST, DEFAULT_CAPABILITIES, DEFAULT_DATA_SOURCE_KEY, DEFAULT_STORAGE_SOURCE_KEY, EntityReference, EntityRelation, FIREBASE_CAPABILITIES, GeoPoint, MONGODB_CAPABILITIES, NULL_OPS, POSTGRES_CAPABILITIES, PUBLIC_STORAGE_PREFIX, REST_TO_CANONICAL, RebaseApiError, RebaseClientError, Vector, getCollectionDataPath, getDataSourceCapabilities, getDeclaredSubcollections, isBranchAdmin, isDocumentAdmin, isFirebaseCollectionConfig, isLazyComponentRef, isMongoDBCollectionConfig, isPostgresCollectionConfig, isPublicStoragePath, isSQLAdmin, isSchemaAdmin, policy, registerDataSourceCapabilities, toCanonicalOp };
 
 //# sourceMappingURL=index.es.js.map