@rebasepro/common 0.16.0 → 0.16.1-canary.g0d7af95

package/dist/collections/CollectionRegistry.d.ts

@@ -1,5 +1,5 @@
 import { CollectionCallbacks, CollectionConfig } from "@rebasepro/types";
-import { DataSourceRegistry } from "../data/resolveDataSource";
+import { DataSourceRegistry } from "../data/resolveDataSource.js";
 export declare class CollectionRegistry {
     /**
      * Declared data sources, used during normalization to resolve each

package/dist/collections/index.d.ts

@@ -1,2 +1,2 @@
-export * from "./CollectionRegistry";
-export * from "./default-collections";
+export * from "./CollectionRegistry.js";
+export * from "./default-collections.js";

package/dist/index.d.ts

@@ -1,11 +1,11 @@
-export * from "./util";
-export * from "./collections";
-export * from "./data/buildRebaseData";
-export * from "./data/buildRoutedRebaseData";
-export * from "./data/resolveDataSource";
-export * from "./data/query_builder";
-export * from "./data/paginate";
-export * from "./data/filter-conditions";
-export * from "./data/filter-dialect";
-export * from "./data/sort-dialect";
-export * from "./table-classification";
+export * from "./util/index.js";
+export * from "./collections/index.js";
+export * from "./data/buildRebaseData.js";
+export * from "./data/buildRoutedRebaseData.js";
+export * from "./data/resolveDataSource.js";
+export * from "./data/query_builder.js";
+export * from "./data/paginate.js";
+export * from "./data/filter-conditions.js";
+export * from "./data/filter-dialect.js";
+export * from "./data/sort-dialect.js";
+export * from "./table-classification.js";

package/dist/index.es.js

@@ -699,8 +699,45 @@ function getTableName(collection) {
 	if (isRelationalCollectionConfig(collection)) return collection.table ?? toSnakeCase(collection.slug) ?? toSnakeCase(collection.name);
 	return toSnakeCase(collection.slug) ?? toSnakeCase(collection.name);
 }
+/**
+* A JavaScript identifier: what a generated `export const <name> =` needs.
+*
+* Deliberately the same shape the two schema generators already define
+* privately — this is the third place that needed it, and the first two guard
+* property keys and member accesses while nothing guarded the variable name
+* itself.
+*/
+var JS_IDENTIFIER = /^[A-Za-z_$][A-Za-z0-9_$]*$/;
+/**
+* The variable name a generated table is bound to.
+*
+* Camel-cases underscores, and then guarantees the result is a legal
+* identifier. It did only the first, so a table name that is legal in Postgres
+* and not in JavaScript produced a `schema.generated.ts` that does not parse:
+*
+*   `2024_archive`       → `export const 2024Archive = pgTable(…)`
+*                          "An identifier or keyword cannot immediately follow
+*                           a numeric literal"
+*   `reporting.events`   → `export const reporting.events = pgTable(…)`
+*                          "',' expected"
+*
+* That file is imported by the server, so the failure is not one broken
+* collection — `rebase build` and `db push` fail at tsc for the whole
+* directory. And it is reachable from a documented flow: `rebase init` against
+* a database holding a table called `2024_archive` writes a collection file
+* that parses and a schema file that does not.
+*
+* **A no-op for every name that already worked**, which is what makes changing
+* a derived name safe here: the only inputs whose output changes are the ones
+* that produced a syntax error, and nothing can be running against those.
+* Separators become camel case rather than disappearing, so `reporting.events`
+* and `reporting_events` do not collide into one variable.
+*/
 function getTableVarName(tableName) {
-	return tableName.replace(/_([a-z])/g, (_, char) => char.toUpperCase());
+	const camel = tableName.replace(/_([a-z])/g, (_, char) => char.toUpperCase());
+	if (JS_IDENTIFIER.test(camel)) return camel;
+	const sanitised = camel.replace(/[^A-Za-z0-9_$]+([A-Za-z0-9])?/g, (_, char) => char ? char.toUpperCase() : "").replace(/^([0-9])/, "t$1");
+	return JS_IDENTIFIER.test(sanitised) ? sanitised : `t${sanitised}`;
 }
 function getEnumVarName(tableName, propName) {
 	return `${getTableVarName(tableName)}${propName.charAt(0).toUpperCase() + propName.slice(1)}`;
@@ -2804,6 +2841,15 @@ var REBASE_USER_ROLE = "rebase_user";
 *
 * `atlas_schema_revisions` is Atlas's migration ledger, which lands in `rebase`
 * because `db migrate apply` passes `--revisions-schema rebase`.
+*
+* Every entry here must also be revoked by whatever creates it, and vice versa:
+* the creation-time revoke fires once, on the boot that first makes the table,
+* so it cannot help a database provisioned before that revoke existed. This
+* list is what the boot-time sweep in `ensureAppRole` iterates, and the sweep
+* is the only thing that can repair an already-granted table. A table revoked
+* at creation but missing here is therefore permanently stranded on any
+* database that predates its revoke — which is exactly what happened to
+* `jobs`, added here after a scan of a pre-0.14 database found it.
 */
 var REBASE_INTERNAL_TABLES = [
 	"user_identities",
@@ -2818,10 +2864,12 @@ var REBASE_INTERNAL_TABLES = [
 	"api_keys",
 	"cron_logs",
 	"cron_claims",
+	"jobs",
 	"rate_limit_hits",
 	"idempotency_keys",
 	"entity_history",
 	"branches",
+	"metric_samples",
 	"channel_messages",
 	"channel_cursors",
 	"channel_presence",
@@ -4543,6 +4591,7 @@ function createDriverAccessor(driver, slug, getPks = () => []) {
 				orderBy: normalizeOrderBy(params?.orderBy),
 				searchString: params?.searchString,
 				searchExplain: params?.searchExplain,
+				vectorSearch: params?.vectorSearch,
 				onUpdate: (entities) => {
 					onUpdate({
 						data: entities.map((row) => rowToEntity(normalize(row), slug, getPks())),