@dforge-core/metadata 0.0.32 → 0.0.33

package/CHANGELOG.md

@@ -7,6 +7,17 @@ and this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **`translations.schema.json`:** `views.<code>` accepts `desc` (the view description) next
+  to `label` (#1301). `TranslationsFile.views` gains `desc?`.
+
+### Removed
+
+- **`isView` / `viewSql` on an entity** (#1312). SQL-view entities were never implemented:
+  the server dropped both keys and installed an empty table. `entity.schema.json` now
+  rejects them, and pack and install refuse them. `EntityDef` loses both fields.
+
 ## [0.0.32] — 2026-09-28
 
 ### Added

package/dist/index.d.ts

@@ -712,12 +712,8 @@ interface EntityDef {
     description?: string;
     /** Database schema name override (defaults to module schema). */
     schema?: string;
-    /** Database table/view name (defaults to entity code). */
+    /** Database table name (defaults to entity code). */
     dbObject?: string;
-    /** When true, maps to a SQL view (read-only, no DDL). */
-    isView?: boolean;
-    /** SELECT statement for view-backed entities (`isView=true`). */
-    viewSql?: string;
     /** Display pattern using column placeholders, e.g. "{first_name} {last_name}". */
     toString?: string;
     /** Audit trail level; overrides the manifest's `auditHistory`. */
@@ -743,9 +739,8 @@ interface EntityDef {
     } & Record<string, unknown>;
     /**
      * Entity views keyed by view name — the platform's column-level security.
-     * Unrelated to `isView`/`viewSql` above (a SQL-view-backed entity) and to
-     * `ui/data_views.json` (grids, kanban, calendars), both of which the word
-     * "view" also names in this platform. A
+     * Unrelated to `ui/data_views.json` (grids, kanban, calendars), which the
+     * word "view" also names in this platform. A
      * folder binds one view per entity through `ui/folders.json`
      * (`entities.<code>.viewName`); users working in that folder see ONLY the
      * columns the view lists. An entity without views (or a folder naming the
@@ -1462,6 +1457,7 @@ interface TranslationsFile {
     }>;
     views?: Record<string, {
         label?: string;
+        desc?: string;
     }>;
     menus?: Record<string, TranslatedMenu>;
     settings?: Record<string, {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dforge-core/metadata",
-	"version": "0.0.32",
+	"version": "0.0.33",
 	"description": "Canonical dForge authoring registries — field types, base datatypes, column types, traits, data-view kinds and chart types — with derivation helpers. Runtime-dependency-free; the single source of truth shared by editors, the web app and the CLI.",
 	"license": "MIT",
 	"author": "dForge",

package/schemas/entity.schema.json

@@ -2,7 +2,7 @@
 	"$schema": "http://json-schema.org/draft-07/schema#",
 	"$id": "https://dforge.dev/schemas/entity.schema.json",
 	"title": "dForge Entity Definition",
-	"description": "Defines an entity (table/view mapping) for a dForge module",
+	"description": "Defines an entity (a table) for a dForge module",
 	"type": "object",
 	"anyOf": [
 		{ "required": ["fields"] },
@@ -24,16 +24,7 @@
 		},
 		"dbObject": {
 			"type": "string",
-			"description": "Database table or view name (defaults to entity code)"
-		},
-		"isView": {
-			"type": "boolean",
-			"description": "When true, entity maps to a SQL view (read-only, no DDL generation). Default: false (table-backed).",
-			"default": false
-		},
-		"viewSql": {
-			"type": "string",
-			"description": "SQL SELECT statement for view-backed entities (isView=true). Executed as CREATE OR REPLACE VIEW during module install."
+			"description": "Database table name (defaults to entity code)"
 		},
 		"toString": {
 			"description": "Display pattern using column placeholders, e.g. \"{first_name} {last_name}\" — the caption of a record wherever it is referenced. Every `{placeholder}` must name a field of the entity (trait columns included) and not a set; pack and install fail otherwise. Omitted, the install generates one from the fields and warns. Not declared on extension entities (with `extends`). No `type` constraint here because `toString` collides with Object.prototype.toString in JSON validators — they read the inherited function and reject it, even when the property is absent from the JSON."
@@ -151,7 +142,7 @@
 		},
 		"views": {
 			"type": "object",
-			"description": "Entity views keyed by view name — column-level security. Unrelated to 'isView'/'viewSql' (a SQL-view-backed entity) and to ui/data_views.json (grids, kanban, calendars). A folder binds one view per entity via ui/folders.json (entities.<code>.viewName); users working in that folder see ONLY the columns the view lists. Entities without views show the entity's full column set; a folder naming a view that isn't declared here FAILS the install, since resolving it to nothing would show every column \u2014 the opposite of what naming a view asks for. A view can only be declared by the entity's own module: an extension ('extends') declaring 'views' is rejected, because a view lists the complete column set and an extension knows only the columns it adds.",
+			"description": "Entity views keyed by view name — column-level security. Unrelated to ui/data_views.json (grids, kanban, calendars). A folder binds one view per entity via ui/folders.json (entities.<code>.viewName); users working in that folder see ONLY the columns the view lists. Entities without views show the entity's full column set; a folder naming a view that isn't declared here FAILS the install, since resolving it to nothing would show every column \u2014 the opposite of what naming a view asks for. A view can only be declared by the entity's own module: an extension ('extends') declaring 'views' is rejected, because a view lists the complete column set and an extension knows only the columns it adds.",
 			"propertyNames": {
 				"pattern": "^[a-zA-Z_][a-zA-Z0-9_-]*$",
 				"maxLength": 100

package/schemas/translations.schema.json

@@ -32,9 +32,9 @@
 		},
 		"views": {
 			"type": "object",
-			"description": "Data view code → label.",
+			"description": "Data view code → label and description (the subtitle under the view title).",
 			"additionalProperties": {
-				"$ref": "#/$defs/labelOnly"
+				"$ref": "#/$defs/labelDesc"
 			}
 		},
 		"menus": {

package/src/entity.ts

@@ -162,12 +162,8 @@ export interface EntityDef {
 	description?: string;
 	/** Database schema name override (defaults to module schema). */
 	schema?: string;
-	/** Database table/view name (defaults to entity code). */
+	/** Database table name (defaults to entity code). */
 	dbObject?: string;
-	/** When true, maps to a SQL view (read-only, no DDL). */
-	isView?: boolean;
-	/** SELECT statement for view-backed entities (`isView=true`). */
-	viewSql?: string;
 	/** Display pattern using column placeholders, e.g. "{first_name} {last_name}". */
 	toString?: string;
 	/** Audit trail level; overrides the manifest's `auditHistory`. */
@@ -191,9 +187,8 @@ export interface EntityDef {
 	params?: { restricted?: boolean } & Record<string, unknown>;
 	/**
 	 * Entity views keyed by view name — the platform's column-level security.
-	 * Unrelated to `isView`/`viewSql` above (a SQL-view-backed entity) and to
-	 * `ui/data_views.json` (grids, kanban, calendars), both of which the word
-	 * "view" also names in this platform. A
+	 * Unrelated to `ui/data_views.json` (grids, kanban, calendars), which the
+	 * word "view" also names in this platform. A
 	 * folder binds one view per entity through `ui/folders.json`
 	 * (`entities.<code>.viewName`); users working in that folder see ONLY the
 	 * columns the view lists. An entity without views (or a folder naming the

package/src/translations.ts

@@ -47,7 +47,7 @@ export interface TranslationsFile {
 	domains?: Record<string, TranslatedWithOptions>;
 	/** Folder code (flat, not the path) → label. */
 	folders?: Record<string, { label?: string }>;
-	views?: Record<string, { label?: string }>;
+	views?: Record<string, { label?: string; desc?: string }>;
 	menus?: Record<string, TranslatedMenu>;
 	settings?: Record<string, { label?: string; desc?: string }>;
 	/** Module-qualified role code → label. */