@dforge-core/metadata 0.0.14 → 0.0.16

package/CHANGELOG.md

@@ -5,6 +5,163 @@ All notable changes to `@dforge-core/metadata` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.0.16] — 2026-08-19
+
+### Added
+
+- **`EntityDef.views`** — entity views, the platform's column-level security, typed as
+  the new exported `EntityViewDef` / `EntityViewColumnDef`. A view is a named subset of
+  an entity's columns; a folder binds one per entity through `ui/folders.json`
+  (`entities.<code>.viewName`, already typed on `FolderEntityDef`), and users working in
+  that folder see ONLY the columns the view lists. The JSON schema gained the property
+  first — this closes the gap where the authoring types could not express a `views`
+  block at all.
+
+  ```jsonc
+  "views": {
+    "accountant": {
+      "columns": {
+        "product_id": {},
+        "name": { "flags": "VOG" },
+        "price": { "flags": "EVO" }
+      }
+    }
+  }
+  ```
+
+  A column ABSENT from `columns` is hidden — that is the mechanism, not an oversight —
+  and the view must list the primary key, since records are addressed by it.
+
+- **`EntityViewColumnDef.formula`** — per-view formula override, in the same DSL as a
+  field's `formula`. Allowed only on a column the entity declares as `columnType: "F"`;
+  on any other column that field holds the SQL default, so an override there would be
+  inert, and the installer rejects it.
+
+### Changed
+
+- **`schemas/entity.schema.json`** re-synced from `docs/schemas/` — it had drifted since
+  `views` was added there, so the shipped copy rejected a block the platform accepts
+  (the schema is `additionalProperties: false`, so editors flagged `views` as an error).
+- **`FolderEntityBinding.viewName` was documented as a data view code** — it is not. It
+  names a key under the entity definition's `views`, and `ui/data_views.json` codes are
+  referenced by menus' `dataViewCode` instead. Corrected here and in
+  `schemas/folders.schema.json`. The word "view" names three different things in this
+  platform (entity views, data views, and `isView`/`viewSql` SQL-backed entities), so
+  both declaration sites now say which one they mean.
+
+### Note for authors
+
+An EMPTY override is not the same as an omitted one. The runtime merges view over entity
+with `COALESCE`, which skips NULL only — so `"flags": ""` means "no flags in this view" (a
+column neither visible nor editable) and `"params": {}` suppresses the entity-level params
+rather than inheriting them. Omit the key entirely to inherit.
+
+## [0.0.15] — 2026-08-17
+
+### Added
+
+- **`ManifestDef.features`** — opt-in platform behaviours a package was authored for,
+  typed as the new exported `ModuleFeature` union. Absent or empty means the
+  pre-feature behaviour for all of them, so a module written before a feature existed
+  keeps working until its author declares it and republishes.
+
+  ```jsonc
+  "features": ["report-security"]
+  ```
+
+  `"report-security"` makes this module's reports require the `E` right on their
+  security object; declare the matching `"report:<code>": "E"` grants in
+  `security/roles.json` first, or the reports go dark for every role. Unknown names
+  are rejected at package load rather than ignored — a misspelled feature would
+  otherwise leave the old behaviour in place while the manifest claims otherwise.
+  `schemas/manifest.schema.json` carries the matching `enum`, and the three lists
+  (schema enum, this union, and the server's `ModuleFeatures`) are edited together.
+
+- **`ParamDef.columnType`** — `"R"` declares a REFERENCE parameter, whose submitted
+  value is the whole picked record rather than its bare key. The JSON counterpart of
+  the action DSL's `paramCd: ref <entityCd>`, stored in the same `param.column_type`.
+  The schema already accepted it; the type did not.
+
+  The choice is not cosmetic: omitting it (a plain `lookup`) submits the key, which is
+  what a filter comparing against a reference column needs, since the server
+  destructures a key object across every key column and ignores non-key fields.
+  Declare `"R"` when the report wants the record itself. Either way the picker is
+  configured by `params.link` (`{ entity, otherKey? }`), and `otherKey` is filled from
+  the target's primary key when omitted — comma-joined and paired POSITIONALLY with
+  the key columns.
+
+- **`matrixViewConfig.calculatedMembers`** (schema) — synthetic read-only rows or
+  columns of a pivot-like view, derived by formula over OTHER members' values at each
+  cross-axis position (a Gross Margin % line, a Q1 total column). The feature shipped
+  some time ago and `gl`'s P&L matrix uses it, but `matrixViewConfig` is
+  `additionalProperties: false`, so declaring it was a validation error — editors
+  flagged a config the platform renders correctly.
+
+  The new `calculatedMember` `$def` mirrors `CalculatedMember` in `@dforge/data`:
+  `key`, `axis` (`row` default / `column`), `label`, `field`, `refs` (bracket-alias →
+  member identity), `formula`, `position`, `depth` and `format`. Platform-generic —
+  any pivot-like surface consumes the same shape, so adding an indicator is config
+  only, evaluated client-side by the stock formula engine.
+
+- **Record-report attachments.** `ReportDef` gains `entities` — an array of
+  `ReportEntityAttachment` (also exported) declaring which entities a report can be
+  opened *from*, with the mapping from report parameter to source column on each. Each
+  entry becomes one `dForge.entity_report` row, and the report opens on a record-scoped
+  route with the record's values feeding its params server-side.
+
+  ```jsonc
+  "credit_check": {
+      "entities": [
+          { "entityCd": "parties.party", "params": { "customer_id": "party_id" }, "orderNum": 45 }
+      ]
+  }
+  ```
+
+  The binding lives on the attachment, not the report: the same report attaches to
+  several entities with different mappings, and reports stay entity-agnostic. A qualified
+  `entityCd` must name a declared dependency; source columns are limited to the PK, a
+  reference (`R`) column, or a bounded scalar, and must be type-compatible with the target
+  param. `schemas/reports.schema.json` carries the matching `entityAttachment` `$def`.
+
+- **`ReportDef.reloadInterval`** — the report's auto-refresh interval in seconds. It has
+  worked since long before this release but was absent from the schema, and since the
+  report object is `additionalProperties: false`, setting it was a validation error.
+
+### Changed — report parameters have a report-level home again
+
+`ReportDef.parameters` is **kept and now implemented**. Parameters are report-scoped
+throughout the platform — the declaration is stored once per report
+(`report.param_set_id` → `param_set`), the authoring API is `report.params.save`, and
+`report.get` flattens per-dataset defaults report-wide before use — but the installer had
+only ever read the per-dataset shorthand, so a report-level block was silently dropped and
+the report installed with no parameters at all.
+
+Both sites are now legal and mean the same thing. The installer merges them into the
+report's single parameter set, **report level winning** on a code collision:
+
+```jsonc
+"customer_statement": {
+    "parameters": {
+        "customer_id": { "label": "Customer", "fieldTypeCd": "lookup",
+                         "params": { "link": { "entity": "parties.party" } }, "required": true }
+    },
+    "datasets": { "statement_invoices": { }, "statement_payments": { } }
+}
+```
+
+Declare a parameter at report level when more than one dataset uses it — there is no
+meaningful dataset to attribute it to, which is why the exporter previously had to dump the
+whole set onto "the first dataset that had params". `datasets.<cd>.params` stays fully
+supported and is the right shorthand when exactly one dataset uses the parameter.
+
+### Removed
+
+- **`paramDef.isRequired` and `paramDef.link`.** Neither is read by the installer: the key
+  is `required` (so `isRequired` installed the parameter as optional), and a lookup's
+  binding nests under `params` as `params.link` (so a top-level `link` installed the
+  parameter with no autocomplete). Unlike `parameters` these are simply misspellings, with
+  a correct spelling already in the schema — so they are gone rather than implemented.
+
 ## [0.0.14] — 2026-08-10
 
 ### Added

package/dist/index.d.ts

@@ -525,6 +525,46 @@ interface EntityReference {
     /** ON UPDATE rule; a no-op for immutable `cuid` PKs. */
     onUpdate?: ReferentialAction;
 }
+/**
+ * Per-view overrides for one column (`views.<name>.columns.<column_cd>`). Every
+ * property is optional; an omitted one falls back to the entity-level value.
+ *
+ * An EMPTY value is not the same as an omitted one — the runtime merges view over
+ * entity with COALESCE, so `flags: ""` means "no flags in this view" (a column
+ * neither visible nor editable) and `params: {}` suppresses the entity-level
+ * params rather than inheriting them.
+ */
+interface EntityViewColumnDef {
+    /** Flag letters for this column in this view, e.g. "VO" to expose it read-only. */
+    flags?: string;
+    orderNum?: number;
+    isNullable?: boolean;
+    editMask?: string;
+    displayFmt?: string;
+    /**
+     * Formula override for this column in this view, same DSL as a field's
+     * `formula`. Only on a column the entity declares as `columnType: "F"` — on any
+     * other column that field is the SQL default, so an override would be inert.
+     */
+    formula?: string;
+    /** Lookup filter override for a reference column in this view. */
+    refFilter?: unknown;
+    /** Control-specific configuration override for this view. */
+    params?: Record<string, unknown>;
+}
+/** One entity view: the columns it exposes, plus optional per-view overrides. */
+interface EntityViewDef {
+    /**
+     * Column code → per-view overrides. Columns ABSENT from this map are hidden in
+     * a folder bound to the view — that is the mechanism, not an oversight. `{}`
+     * (or null) exposes a column with no overrides. Must include the entity's
+     * primary key: records are addressed by it (hide it by omitting `V` from its
+     * flags instead).
+     */
+    columns: Record<string, EntityViewColumnDef | null>;
+    /** Free-form view configuration, stored on entity_view.params. */
+    params?: Record<string, unknown>;
+}
 /** Automatic document numbering config (entity `numberSequence`). */
 interface NumberSequenceDef {
     /** Column code that receives the auto-generated number. */
@@ -620,6 +660,17 @@ 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
+     * 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
+     * conventional `"default"`, which declares nothing) shows the full column set.
+     */
+    views?: Record<string, EntityViewDef>;
 }
 
 /** `{ field, target }` for each Reference (R) column that declares a link. */
@@ -742,27 +793,45 @@ interface ParamDefBase {
     label?: string;
     /** Display order in the parameter form (falls back to declaration order). */
     orderNum?: number;
-    /** Whether the user must provide a value. */
+    /**
+     * Whether the user must provide a value. Stored inverted as `param.is_nullable`.
+     * There is no `isRequired` spelling — the installer reads this key only.
+     */
     required?: boolean;
-    /** Alternate spelling of `required` used by some modules. Prefer `required`. */
-    isRequired?: boolean;
     /** Default value applied when the user doesn't provide one. */
     default?: unknown;
-    /** Entity link for lookup-type params. */
-    link?: {
-        entity: string;
-        otherKey?: string;
-    };
     /**
-     * Field-type-specific params — most importantly `options` for a dropdown.
+     * Field-type-specific params, nested under this key — there is no top-level
+     * `link`. A lookup param needs `{ link: { entity, otherKey? } }`.
+     * Most importantly `options` for a dropdown.
      * Options accept the same rich `{value,label,icon,color}` form entity columns
      * use; a bare string list renders the raw codes in every locale, so label them.
      * Omitted on a domain-backed param: the domain owns the list.
      */
     params?: Record<string, unknown>;
+    /**
+     * Declares a REFERENCE parameter: the submitted value is the whole picked
+     * record rather than its bare key. The JSON counterpart of the action DSL's
+     * `paramCd: ref <entityCd>`, stored in the same `param.column_type`.
+     *
+     * Optional, and the choice is not cosmetic. Omitting it (a plain `lookup`)
+     * submits the key, which is what a filter comparing against a reference
+     * column needs — the server destructures a key object across every key
+     * column and ignores non-key fields. Declare `"R"` when the report wants the
+     * record itself, not just its identity.
+     *
+     * Either way the picker is configured by `params.link` (`{ entity, otherKey? }`);
+     * `otherKey` is filled from the target's primary key when omitted, comma-joined
+     * and paired POSITIONALLY with the key columns.
+     */
+    columnType?: "R";
 }
 /**
- * A report parameter definition (report- or dataset-level).
+ * A report parameter definition. Declared in the report-level `parameters` block,
+ * or as shorthand under the `params` of the dataset that consumes it — the
+ * installer merges both into the report's single param set, so either way the
+ * parameter serves the whole report. Report level wins on a code collision, and
+ * is the only sensible home for a parameter several datasets use.
  *
  * A parameter takes its control from an explicit `fieldTypeCd` **or** from a
  * column `domain` — never both. Declaring both is the one rejected combination
@@ -815,9 +884,40 @@ interface Dataset {
     procedureName?: string;
     /** Optional column metadata overrides: field code → override. */
     columnsDef?: Record<string, ColumnDef>;
-    /** Dataset-level parameters (alternative to report-level `parameters`). */
+    /**
+     * Parameters declared on this dataset — shorthand for the report-level
+     * `parameters` block, convenient when exactly one dataset uses the parameter.
+     * The installer merges both into the report's one param set either way.
+     */
     params?: Record<string, ParamDef>;
 }
+/**
+ * One (entity, report) **record-report attachment**: the report becomes openable
+ * from that entity's record, with the record's values feeding its parameters.
+ * Each entry becomes one `dForge.entity_report` row.
+ *
+ * The binding is per-attachment, not per-report — the same report can attach to
+ * several entities with different parameter mappings, which is why the mapping
+ * lives here rather than on the report.
+ */
+interface ReportEntityAttachment {
+    /**
+     * Entity the report attaches to, qualified `module.entity` for anything
+     * outside the declaring module. That module must be a declared dependency.
+     */
+    entityCd: string;
+    /**
+     * Parameter mapping: report param code → **source column on the entity**.
+     * (Not a param declaration — those live in the report's `parameters` block or a
+     * dataset's `params`.) Resolved server-side
+     * from the record's PK. Source columns are limited to the PK, reference (`R`)
+     * columns, and bounded scalars; source and target must be type-compatible.
+     * Params left unmapped keep their normal behaviour (default, or prompt).
+     */
+    params?: Record<string, string>;
+    /** Sort position in the record's combined action + report menu. */
+    orderNum?: number;
+}
 /** A single visualization panel within the report layout. */
 interface ReportPanel {
     vizType: VizType;
@@ -837,8 +937,21 @@ interface ReportDef {
     layout: ReportLayout;
     /** Dataset code → dataset definition. */
     datasets: Record<string, Dataset>;
-    /** Report-level parameters (alternative to per-dataset `params`). */
+    /** Auto-refresh interval in seconds. Omit (or 0) for no auto-refresh. */
+    reloadInterval?: number;
+    /**
+     * Report-level parameter declarations — the canonical home for a parameter, and
+     * the only one that fits a parameter several datasets use. Merged with each
+     * dataset's `params` into the report's single param set; this block wins on a
+     * code collision.
+     */
     parameters?: Record<string, ParamDef>;
+    /**
+     * Record-report attachments: entities this report can be opened from, with the
+     * mapping from report parameter to source column on each. Omit for a report
+     * that is only reached from a menu.
+     */
+    entities?: ReportEntityAttachment[];
 }
 /** A `ui/reports.json` file: report code → definition. */
 type ReportsFile = Record<string, ReportDef>;
@@ -853,6 +966,12 @@ type ModuleDependency = string | {
     version: string;
     entities?: string[];
 };
+/**
+ * A platform behaviour a package can opt into via `manifest.features`.
+ * Mirrors `dForge.Core.ModuleFeatures` and the `features` enum in
+ * manifest.schema.json — all three are edited together.
+ */
+type ModuleFeature = "report-security";
 /** A module package manifest (`manifest.json`). */
 interface ManifestDef {
     /** Package format version (currently 1). */
@@ -890,6 +1009,20 @@ interface ManifestDef {
     icon?: string;
     /** Non-English locales the package promises to translate. */
     supportedLocales?: string[];
+    /**
+     * Opt-in platform behaviours this package was authored for. Absent or empty
+     * = the pre-feature behaviour for all of them, so a module written before a
+     * feature existed keeps working until its author declares it and republishes.
+     *
+     * Unknown names are rejected at package load, never ignored — a misspelled
+     * feature would silently leave the old behaviour in place while the manifest
+     * claims otherwise.
+     *
+     * - `report-security` — this module's reports require 'E' on their
+     *   `sec_object`. Declare the matching `"report:<code>": "E"` grants in
+     *   `security/roles.json` first, or the reports go dark for every role.
+     */
+    features?: ModuleFeature[];
     /** Initial creation date (YYYY-MM-DD). Informational. */
     created?: string;
     /** Last manifest edit date (YYYY-MM-DD). Informational. */
@@ -1016,7 +1149,16 @@ type MenusFile = Record<string, MenuDef>;
 
 /** Per-entity binding within a folder. */
 interface FolderEntityBinding {
-    /** Data view code to use in this folder (commonly 'default'). */
+    /**
+     * Entity view to bind for this entity in this folder — a key under the entity
+     * definition's `views` (see `EntityViewDef`), NOT a data view code from
+     * `ui/data_views.json`. Users in this folder then see only the columns that
+     * view lists.
+     *
+     * The conventional `"default"` declares nothing and means "no view" (the full
+     * column set); any other name the entity does not declare fails the install,
+     * since falling back would grant more access than naming a view asks for.
+     */
     viewName?: string;
     /** Enable the quick-add (+) button for this entity here. */
     quickAdd?: boolean;
@@ -1234,13 +1376,41 @@ interface ActionDef {
     executionMode: ActionExecutionMode;
     /** DSL script name (file under `logic/actions/<script>.dsl`). */
     script: string;
-    /** Run inside a transaction (failures roll back). */
+    /**
+     * Run the whole selection in one transaction, so a failure on any record
+     * rolls back the records already processed. **Defaults to `true`** when
+     * omitted (`ActionDef.IsTransacted` in the installer is a non-nullable
+     * `bool` initialised to `true`), so omit it only when you want atomicity.
+     *
+     * `false` opens no transaction, and what follows a failure depends on
+     * {@link ActionDef.executionMode}: `single` / `each` report it and continue
+     * with the next record, so use that for independent per-record work that
+     * should process as many records as pass; `batch` is a single script
+     * invocation with no loop to continue, so the run simply ends with its
+     * earlier writes committed.
+     *
+     * On a run queued to the background the **rollback** guarantee is lost
+     * outright — the worker opens no transaction, so nothing is ever undone. What
+     * remains of the flag there depends on the mode: the worker's `single`/`each`
+     * loop still reads it for control flow (stop after the first failed record vs.
+     * continue), while its `batch` path never reads it at all — one invocation,
+     * which ends on failure under either value.
+     */
     isTransacted?: boolean;
     /** Display order. */
     orderNum?: number;
-    /** Run in the background (newer `async`; some modules use `isAsync`). */
+    /**
+     * @deprecated Not read by the installer — use {@link ActionDef.isAsync}.
+     * The module manifest model binds `isAsync` only, so this key is silently
+     * ignored and the action installs as synchronous.
+     */
     async?: boolean;
-    /** Alternate spelling of `async` used by some modules. Prefer `async`. */
+    /**
+     * Permit background execution. It does not force it: `action.execute`
+     * carries its own `async` argument and the server branches on that, so an
+     * action with parameters is offered to the user as both "Run" (inline) and
+     * "Run in Background". A parameterless `isAsync` action is queued directly.
+     */
     isAsync?: boolean;
 }
 /** A `ui/actions.json` file: action code → definition. */
@@ -1251,4 +1421,4 @@ declare const flagDefs: readonly {
     label: string;
 }[];
 
-export { AGG_TYPE_LIST, type AccumulationConfig, type ActionDef, type ActionExecutionMode, type ActionsFile, AggType, type AlignType, type BaseDatatypeCd, type CalendarViewConfig, type ColumnDef, type ColumnTypeCd, type ColumnTypeDef, DEP_COLUMN_TYPES, type DataSource, type DataViewDef, type DataViewsFile, type Dataset, type DepColumn, type DepColumnMode, type DepColumnType, type DepEntity, type DepProvenance, type DepProvenanceKind, type DepsFile, type DeriveOptions, type DiagramViewConfig, type DomainDef, type DomainsFile, type EntityDef, type EntityEvent, type EntityReference, FILTER_GROUP_OPERATORS, FILTER_OPERATORS, type FieldDef, type FieldLink, type FieldOption, type FieldTypeCd, type FieldTypeDef, type Filter, type FilterCondition, type FilterGroup, type FilterGroupOperator, type FilterOperator, type FlagCd, type FolderDef, type FolderEntityBinding, type FoldersFile, type JobDef, type JobsFile, type KanbanViewConfig, type LedgerRegistryEntry, type ListLevelConfig, type ListViewConfig, type ManifestAuthor, type ManifestDef, type MenuDef, type MenuItemDef, type MenuItemType, type MenusFile, type ModuleDependency, NUMERIC_TOTAL, type NamedKind, type NumberSequenceDef, type ParamDef, type ParamDefBase, type PeriodConfig, type PrintMargins, type PrintPageSettings, type PrintTemplateDef, type PrintTemplatesFile, type ReportDef, type ReportLayout, type ReportPanel, type ReportQuery, type ReportsFile, type RoleDef, type RolesFile, type SeedDataFile, type SettingBaseDatatype, type SettingDef, type SettingsFile, type SignConfig, type SortClause, type TraitCd, type TraitDef, type TreeGridViewConfig, type TriggerDef, type TriggersFile, type ViewColumn, type ViewType, type VizType, type WebhookPayload, type WebhookSubscription, type WebhooksFile, baseDatatypes, baseToDbDatatype, chartTypes, columnTypes, dataViewKinds, defaultParams, deriveBaseDatatype, deriveDbDatatype, expandTrait, expandTraits, fieldTypeCds, fieldTypes, fieldTypesByColumnType, flagDefs, getColumnType, getFieldType, getIdentityKeys, getLinks, getPrimaryKeys, getTrait, isFieldTypeCd, traits, vizTypes };
+export { AGG_TYPE_LIST, type AccumulationConfig, type ActionDef, type ActionExecutionMode, type ActionsFile, AggType, type AlignType, type BaseDatatypeCd, type CalendarViewConfig, type ColumnDef, type ColumnTypeCd, type ColumnTypeDef, DEP_COLUMN_TYPES, type DataSource, type DataViewDef, type DataViewsFile, type Dataset, type DepColumn, type DepColumnMode, type DepColumnType, type DepEntity, type DepProvenance, type DepProvenanceKind, type DepsFile, type DeriveOptions, type DiagramViewConfig, type DomainDef, type DomainsFile, type EntityDef, type EntityEvent, type EntityReference, type EntityViewColumnDef, type EntityViewDef, FILTER_GROUP_OPERATORS, FILTER_OPERATORS, type FieldDef, type FieldLink, type FieldOption, type FieldTypeCd, type FieldTypeDef, type Filter, type FilterCondition, type FilterGroup, type FilterGroupOperator, type FilterOperator, type FlagCd, type FolderDef, type FolderEntityBinding, type FoldersFile, type JobDef, type JobsFile, type KanbanViewConfig, type LedgerRegistryEntry, type ListLevelConfig, type ListViewConfig, type ManifestAuthor, type ManifestDef, type MenuDef, type MenuItemDef, type MenuItemType, type MenusFile, type ModuleDependency, type ModuleFeature, NUMERIC_TOTAL, type NamedKind, type NumberSequenceDef, type ParamDef, type ParamDefBase, type PeriodConfig, type PrintMargins, type PrintPageSettings, type PrintTemplateDef, type PrintTemplatesFile, type ReportDef, type ReportEntityAttachment, type ReportLayout, type ReportPanel, type ReportQuery, type ReportsFile, type RoleDef, type RolesFile, type SeedDataFile, type SettingBaseDatatype, type SettingDef, type SettingsFile, type SignConfig, type SortClause, type TraitCd, type TraitDef, type TreeGridViewConfig, type TriggerDef, type TriggersFile, type ViewColumn, type ViewType, type VizType, type WebhookPayload, type WebhookSubscription, type WebhooksFile, baseDatatypes, baseToDbDatatype, chartTypes, columnTypes, dataViewKinds, defaultParams, deriveBaseDatatype, deriveDbDatatype, expandTrait, expandTraits, fieldTypeCds, fieldTypes, fieldTypesByColumnType, flagDefs, getColumnType, getFieldType, getIdentityKeys, getLinks, getPrimaryKeys, getTrait, isFieldTypeCd, traits, vizTypes };