ngx-dynamic-entity-builder 2.1.0 → 2.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngx-dynamic-entity-builder",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Angular standalone visual builder for authoring dynamic-entity EntityConfig (fields, tabs, validators, RBAC).",
   "//typings": "Local workspace resolution only: ng-packagr 21 writes types/ngx-dynamic-entity-builder.d.ts into dist/package.json. Do NOT add a 'main' field here — ng-packagr does not generate one, so it would be copied verbatim and resolve wrongly in the published package.",
   "typings": "types/ngx-dynamic-entity-builder.d.ts",
@@ -10,8 +10,8 @@
     "@angular/core": "^17.2.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
     "@angular/forms": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
     "@angular/material": "^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^22.0.0",
-    "@dynamic-entity/core": "^2.1.0",
-    "ngx-dynamic-entity": "^2.1.0",
+    "@dynamic-entity/core": "^2.2.0",
+    "ngx-dynamic-entity": "^2.2.0",
     "rxjs": "^7.0.0"
   },
   "keywords": [

package/types/ngx-dynamic-entity-builder.d.ts

@@ -44,45 +44,18 @@ declare class BuilderStore {
     /**
      * Roles of the person using the builder — distinct from `availableRoles`, which is the
      * vocabulary a schema may reference. Needed so the SYSTEM_DEFAULT_CAN_EDIT predicate can
-     * be asked a real question; it was previously called with a hardcoded empty array, which
-     * made any role-checking predicate answer false for everyone.
+     * be asked a real question rather than answering for an empty role list.
      */
     private readonly _userRoles;
     private readonly history;
-    private readonly cursor;
-    private readonly historyLength;
-    private lastEditAt;
-    /** Consecutive edits closer together than this fold into one undo step. */
-    private static readonly COALESCE_MS;
     readonly canUndo: _angular_core.Signal<boolean>;
     readonly canRedo: _angular_core.Signal<boolean>;
-    /**
-     * Fold the current state into history.
-     *
-     * Called explicitly by the write paths rather than from an `effect`. An effect would have
-     * been fewer call sites, but it requires an injection context: `BuilderStore` had no
-     * constructor, so `new BuilderStore()` was legal, and adding one broke every caller that
-     * did it with NG0203. Explicit calls also make the timing deterministic — a test can
-     * assert straight after an edit instead of flushing effects first.
-     *
-     * Calling it twice for one operation is harmless: the second call sees the same signal
-     * references already at the cursor and returns.
-     *
-     * `setFieldLabel` is bound to a keystroke, so recording every emission would make undo
-     * walk back one character at a time. Two consecutive edits merge when they land inside
-     * `COALESCE_MS` *and* the structure is unchanged — a rename coalesces, while adding,
-     * removing or moving anything always earns its own step however fast it is clicked.
-     */
     private record;
-    /** How many undo steps are kept. */
-    private static readonly MAX_HISTORY;
-    /** Counts that distinguish a structural edit from a value edit. */
-    private shapeOf;
     /** Start history again from the state just loaded. Nothing before it is undoable. */
     private resetHistory;
     undo(): void;
     redo(): void;
-    private applyHistory;
+    private restore;
     readonly config: _angular_core.Signal<EntityFormConfig>;
     readonly selectedFieldId: _angular_core.Signal<string>;
     readonly activeLanguage: _angular_core.Signal<string>;
@@ -93,11 +66,8 @@ declare class BuilderStore {
     /**
      * Every field the config declares, sub-tabs included.
      *
-     * This used to stop at top-level tabs, which quietly broke three things at once: nine of
-     * `insuranceClaims`'s twenty-eight fields never appeared on the canvas, the entity-reference
-     * picker could not offer a nested field as a source, and the drift check looked a nested
-     * field up here, got nothing, and returned without checking. The store's structural
-     * operations already walked the whole tree — only this view did not.
+     * The canvas, the entity-reference source picker and the drift check all read this, so it
+     * has to reach nested tabs just as the store's structural operations do.
      *
      * It deliberately does not descend into a field's own `children`: `group` and `array`
      * children are rendered by the row that owns them, not as rows of their own.
@@ -131,10 +101,9 @@ declare class BuilderStore {
     /**
      * Every tab in the tree, flattened.
      *
-     * The structural operations below used to iterate `draft.tabs` directly, which is only
-     * the top level. A field on a sub-tab could be selected and edited but never removed,
-     * duplicated, moved or reordered — the builder could author nested configs it was then
-     * unable to restructure, which is the worst possible state for an authoring tool.
+     * The structural operations below go through this rather than `draft.tabs`, which is only
+     * the top level — otherwise a field on a sub-tab could be edited but never removed,
+     * duplicated, moved or reordered.
      */
     private flattenTabs;
     /**
@@ -192,14 +161,11 @@ declare class BuilderStore {
      *
      * Ids are the wiring between fields — rules, cascades, patches and `showWhen` all address
      * fields by id — so a rename that only touches `field.id` silently breaks that wiring.
-     * That was survivable while renaming was a rare manual act; label-derived ids make it
-     * routine, so the references move with it.
-     */
-    /**
+     * Label-derived ids make renaming routine, so the references move with it.
+     *
      * `key` addresses the field to rename; `oldId` is the bare id every *reference* to it
-     * carries. They were one parameter, which worked only while an id was unique across the
-     * config: resolving needs the path, while `showWhen`, `parentField`, `autoPatch` targets
-     * and rules are all keyed by bare id and never match a path.
+     * carries. They are separate because resolving needs the path, while `showWhen`,
+     * `parentField`, `autoPatch` targets and rules are all keyed by bare id.
      */
     private applyRename;
     removeField(key: string): void;
@@ -269,7 +235,7 @@ declare class BuilderStore {
     setFieldDataSource(fieldId: string, source: 'none' | 'manual' | 'lookup'): void;
     /** Set the named list a choice field reads its options from. */
     setListName(fieldId: string, listName: string): void;
-    /** Link a field to a field defined in another entity configuration (Phase 8). */
+    /** Link a field to a field defined in another entity configuration */
     linkReferencedField(fieldId: string, sourceEntityKey: string, sourceField: NestedFieldConfig): void;
     /** Unlink a referenced field back to an independent field. */
     unlinkReferencedField(fieldId: string): void;
@@ -485,6 +451,8 @@ declare const DEFAULT_BUILDER_TEXT: {
     hintInLanguage: string;
     hintHint: string;
     defaultValue: string;
+    sliderStep: string;
+    sliderStepHint: string;
     sectionBasics: string;
     sectionLayout: string;
     sectionValidation: string;
@@ -809,11 +777,8 @@ interface PaletteSection {
 /**
  * FieldPaletteComponent — the list of buildable field types.
  *
- * Two things changed the day this stopped being a flat grid of twenty-two buttons. The labels
- * were clipped mid-word — "Boolean Toggl", "Entity Referen", "File Attachmen" — because the
- * grid forced two equal columns and the button refused to wrap, so a third of the palette
- * could not be read. And with no order to them, finding "Month & Year" meant scanning the
- * whole list: the grouping and the filter are what make a palette this size navigable.
+ * Grouped and filterable, because a flat list of twenty-two types is not navigable, and
+ * tiles wrap their labels so names like "Entity Reference" are never clipped.
  */
 declare class FieldPaletteComponent {
     /** Builder chrome, overridable via BUILDER_TEXT. */
@@ -940,6 +905,8 @@ declare class FieldInspectorComponent {
      * put a 1 on every field in the config and tell the author nothing.
      */
     protected displayFlagCount(field: NestedFieldConfig): number;
+    /** A step must be above zero; anything else clears it, and the slider uses 1. */
+    protected positiveOrUnset(value: unknown): number | undefined;
     protected toNum(value: unknown): number | null;
     protected labelValue(field: NestedFieldConfig): string;
     protected placeholderValue(field: NestedFieldConfig): string;
@@ -980,9 +947,7 @@ declare class FieldInspectorComponent {
     }[];
     /**
      * Seeds a new condition with the first field not already watched.
-     *
-     * It used to seed the literal string `field`, which is not a field id at all — so a new
-     * condition started out referencing nothing and silently hid the field until it was edited.
+     * A seed that names no real field would silently hide this one until edited.
      */
     protected addShowWhen(field: NestedFieldConfig): void;
     protected renameShowWhen(field: NestedFieldConfig, oldKey: string, newKey: string): void;