@clivly/core 0.10.6 → 0.10.7

package/dist/entity-heuristics.cjs

@@ -283,6 +283,54 @@ const SENSITIVE_COLUMNS = /* @__PURE__ */ new Set([
 function hasSensitiveColumns(columns) {
 	return columns.some((column) => SENSITIVE_COLUMNS.has(column.toLowerCase().replaceAll("-", "_")));
 }
+/**
+* Table names the supported auth libraries create.
+*
+* `hasSensitiveColumns` cannot catch these. Better Auth's `organization` table
+* is `{id, name, slug, logo}` — no credential column anywhere, a real `name`,
+* and "organizations" is in the company vocabulary above. It is, by every
+* signal this module has, an excellent company candidate. On `vue-academy`
+* `clivly init` duly chose it over `campuses`, the actual business table that
+* every student row points at, and the first sync exported rows nothing could
+* receive.
+*
+* Matched on name, deliberately, and this is the inverse of the rule above:
+* withholding a table on a wrong guess is a real loss, so that is decided on
+* columns; *ranking* one below another is cheap to get wrong, so a name match
+* is enough. These are fixed names the plugins create, and an app whose own
+* business table is called `member` still ranks — just after its rivals.
+*/
+const FRAMEWORK_TABLE_NAMES = /* @__PURE__ */ new Set([
+	"account",
+	"session",
+	"user",
+	"verification",
+	"invitation",
+	"member",
+	"organization",
+	"team",
+	"team_member",
+	"apikey",
+	"api_key",
+	"jwks",
+	"passkey",
+	"rate_limit",
+	"ratelimit",
+	"two_factor",
+	"twofactor",
+	"__drizzle_migrations",
+	"drizzle_migrations"
+]);
+/**
+* Is this table one your auth library created, rather than one you wrote?
+*
+* Used to rank such tables below the developer's own when both could serve a
+* concept. Never to exclude them: mapping `user` as the contact entity is
+* legitimate for plenty of apps, and it stays selectable.
+*/
+function isFrameworkTable(name) {
+	return FRAMEWORK_TABLE_NAMES.has(name.toLowerCase().replaceAll("-", "_"));
+}
 function metaFor(table, column) {
 	return table.columnsMeta?.find((c) => c.name === column);
 }
@@ -497,6 +545,7 @@ function toFieldMap(scored) {
 exports.TARGET_CONCEPTS = TARGET_CONCEPTS;
 exports.hasDefiningColumn = hasDefiningColumn;
 exports.hasSensitiveColumns = hasSensitiveColumns;
+exports.isFrameworkTable = isFrameworkTable;
 exports.matchesConcept = matchesConcept;
 exports.requiredFieldsFor = requiredFieldsFor;
 exports.scoreConcepts = scoreConcepts;

package/dist/entity-heuristics.d.cts

@@ -19,6 +19,14 @@ interface ScoredTable {
  * They stay manually selectable — an explicit, informed choice is legitimate.
  */
 declare function hasSensitiveColumns(columns: string[]): boolean;
+/**
+ * Is this table one your auth library created, rather than one you wrote?
+ *
+ * Used to rank such tables below the developer's own when both could serve a
+ * concept. Never to exclude them: mapping `user` as the contact entity is
+ * legitimate for plenty of apps, and it stays selectable.
+ */
+declare function isFrameworkTable(name: string): boolean;
 declare function hasDefiningColumn(concept: TargetConcept, columns: string[]): boolean;
 declare function scoreConcepts(table: ScoredTable): Scored<TargetConcept>[];
 declare function topConcept(table: ScoredTable): {
@@ -61,4 +69,4 @@ interface FieldSuggestion {
 declare function scoreFieldMap(concept: TargetConcept, table: ScoredTable): Scored<FieldSuggestion>[];
 declare function toFieldMap(scored: Scored<FieldSuggestion>[]): Record<string, string>;
 //#endregion
-export { type DiscoveredColumnMeta, FieldSuggestion, RelationshipSuggestion, ScoredTable, SuggestedVia, TARGET_CONCEPTS, TargetConcept, hasDefiningColumn, hasSensitiveColumns, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };
+export { type DiscoveredColumnMeta, FieldSuggestion, RelationshipSuggestion, ScoredTable, SuggestedVia, TARGET_CONCEPTS, TargetConcept, hasDefiningColumn, hasSensitiveColumns, isFrameworkTable, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };

package/dist/entity-heuristics.d.mts

@@ -19,6 +19,14 @@ interface ScoredTable {
  * They stay manually selectable — an explicit, informed choice is legitimate.
  */
 declare function hasSensitiveColumns(columns: string[]): boolean;
+/**
+ * Is this table one your auth library created, rather than one you wrote?
+ *
+ * Used to rank such tables below the developer's own when both could serve a
+ * concept. Never to exclude them: mapping `user` as the contact entity is
+ * legitimate for plenty of apps, and it stays selectable.
+ */
+declare function isFrameworkTable(name: string): boolean;
 declare function hasDefiningColumn(concept: TargetConcept, columns: string[]): boolean;
 declare function scoreConcepts(table: ScoredTable): Scored<TargetConcept>[];
 declare function topConcept(table: ScoredTable): {
@@ -61,4 +69,4 @@ interface FieldSuggestion {
 declare function scoreFieldMap(concept: TargetConcept, table: ScoredTable): Scored<FieldSuggestion>[];
 declare function toFieldMap(scored: Scored<FieldSuggestion>[]): Record<string, string>;
 //#endregion
-export { type DiscoveredColumnMeta, FieldSuggestion, RelationshipSuggestion, ScoredTable, SuggestedVia, TARGET_CONCEPTS, TargetConcept, hasDefiningColumn, hasSensitiveColumns, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };
+export { type DiscoveredColumnMeta, FieldSuggestion, RelationshipSuggestion, ScoredTable, SuggestedVia, TARGET_CONCEPTS, TargetConcept, hasDefiningColumn, hasSensitiveColumns, isFrameworkTable, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };

package/dist/entity-heuristics.mjs

@@ -282,6 +282,54 @@ const SENSITIVE_COLUMNS = /* @__PURE__ */ new Set([
 function hasSensitiveColumns(columns) {
 	return columns.some((column) => SENSITIVE_COLUMNS.has(column.toLowerCase().replaceAll("-", "_")));
 }
+/**
+* Table names the supported auth libraries create.
+*
+* `hasSensitiveColumns` cannot catch these. Better Auth's `organization` table
+* is `{id, name, slug, logo}` — no credential column anywhere, a real `name`,
+* and "organizations" is in the company vocabulary above. It is, by every
+* signal this module has, an excellent company candidate. On `vue-academy`
+* `clivly init` duly chose it over `campuses`, the actual business table that
+* every student row points at, and the first sync exported rows nothing could
+* receive.
+*
+* Matched on name, deliberately, and this is the inverse of the rule above:
+* withholding a table on a wrong guess is a real loss, so that is decided on
+* columns; *ranking* one below another is cheap to get wrong, so a name match
+* is enough. These are fixed names the plugins create, and an app whose own
+* business table is called `member` still ranks — just after its rivals.
+*/
+const FRAMEWORK_TABLE_NAMES = /* @__PURE__ */ new Set([
+	"account",
+	"session",
+	"user",
+	"verification",
+	"invitation",
+	"member",
+	"organization",
+	"team",
+	"team_member",
+	"apikey",
+	"api_key",
+	"jwks",
+	"passkey",
+	"rate_limit",
+	"ratelimit",
+	"two_factor",
+	"twofactor",
+	"__drizzle_migrations",
+	"drizzle_migrations"
+]);
+/**
+* Is this table one your auth library created, rather than one you wrote?
+*
+* Used to rank such tables below the developer's own when both could serve a
+* concept. Never to exclude them: mapping `user` as the contact entity is
+* legitimate for plenty of apps, and it stays selectable.
+*/
+function isFrameworkTable(name) {
+	return FRAMEWORK_TABLE_NAMES.has(name.toLowerCase().replaceAll("-", "_"));
+}
 function metaFor(table, column) {
 	return table.columnsMeta?.find((c) => c.name === column);
 }
@@ -493,4 +541,4 @@ function toFieldMap(scored) {
 	return map;
 }
 //#endregion
-export { TARGET_CONCEPTS, hasDefiningColumn, hasSensitiveColumns, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };
+export { TARGET_CONCEPTS, hasDefiningColumn, hasSensitiveColumns, isFrameworkTable, matchesConcept, requiredFieldsFor, scoreConcepts, scoreFieldMap, scoreRelationships, suggestCursorField, suggestDiscriminatorColumns, toFieldMap, topConcept, validateMapping };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clivly/core",
-  "version": "0.10.6",
+  "version": "0.10.7",
   "private": false,
   "description": "ORM/auth-agnostic CRM adapter contracts and shared domain types for Clivly.",
   "license": "MIT",