@clivly/sdk 0.11.0 → 0.12.0

package/dist/drizzle.cjs

@@ -141,6 +141,7 @@ function fromDrizzle(db, table, opts) {
 	const idColumnName = idColumn.name;
 	const source = {
 		entity: opts.entity,
+		...opts.pushSource === void 0 ? {} : { pushSource: opts.pushSource },
 		cursorField: cursorColumnName,
 		idField: idColumnName,
 		fetchPage: ({ since, limit }) => drizzleDb.select(projection).from(table).where(since ? drizzle_orm.sql`(${cursorColumn}, ${idColumn}) > (${since.time}, ${since.id})` : void 0).orderBy((0, drizzle_orm.asc)(cursorColumn), (0, drizzle_orm.asc)(idColumn)).limit(limit),

package/dist/drizzle.d.cts

@@ -82,6 +82,21 @@ interface FromDrizzleOptions {
    * check and a false explanation.
    */
   objectType?: string;
+  /**
+   * The label this source's pushes carry, when it differs from `entity`.
+   *
+   * `entity` is the CURSOR KEY — two sources sharing it share a cursor, so the
+   * first to run advances it and the second silently pushes nothing. The push
+   * LABEL is matched against a mapping's `sourceTable`, which is the host
+   * table name. Those two requirements conflict whenever one table feeds two
+   * concepts: an `organization` table mapped as both a company and a
+   * subscription deal needs distinct cursors but the same table name on the
+   * wire.
+   *
+   * `fromDrizzleProjection` stamps this itself for the projection case. This
+   * is the same escape hatch for a plain single-table source.
+   */
+  pushSource?: string;
 }
 /**
  * Build a `SyncSource` from a Drizzle table, generating the keyset-paginated

package/dist/drizzle.d.mts

@@ -82,6 +82,21 @@ interface FromDrizzleOptions {
    * check and a false explanation.
    */
   objectType?: string;
+  /**
+   * The label this source's pushes carry, when it differs from `entity`.
+   *
+   * `entity` is the CURSOR KEY — two sources sharing it share a cursor, so the
+   * first to run advances it and the second silently pushes nothing. The push
+   * LABEL is matched against a mapping's `sourceTable`, which is the host
+   * table name. Those two requirements conflict whenever one table feeds two
+   * concepts: an `organization` table mapped as both a company and a
+   * subscription deal needs distinct cursors but the same table name on the
+   * wire.
+   *
+   * `fromDrizzleProjection` stamps this itself for the projection case. This
+   * is the same escape hatch for a plain single-table source.
+   */
+  pushSource?: string;
 }
 /**
  * Build a `SyncSource` from a Drizzle table, generating the keyset-paginated

package/dist/drizzle.mjs

@@ -140,6 +140,7 @@ function fromDrizzle(db, table, opts) {
 	const idColumnName = idColumn.name;
 	const source = {
 		entity: opts.entity,
+		...opts.pushSource === void 0 ? {} : { pushSource: opts.pushSource },
 		cursorField: cursorColumnName,
 		idField: idColumnName,
 		fetchPage: ({ since, limit }) => drizzleDb.select(projection).from(table).where(since ? sql`(${cursorColumn}, ${idColumn}) > (${since.time}, ${since.id})` : void 0).orderBy(asc(cursorColumn), asc(idColumn)).limit(limit),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clivly/sdk",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "private": false,
   "description": "Clivly SDK — connect your app to Clivly Cloud (heartbeat, discovery, auth bridge).",
   "license": "MIT",
@@ -53,7 +53,7 @@
     "README.md"
   ],
   "dependencies": {
-    "@clivly/core": "0.11.0"
+    "@clivly/core": "0.12.0"
   },
   "devDependencies": {
     "@electric-sql/pglite": "^0.5.4",