@yuuvis/client-framework 2.20.1 → 3.0.0-beta.20.0

package/list/lib/list.component.d.ts

@@ -1,320 +0,0 @@
-import { BooleanInput } from '@angular/cdk/coercion';
-import { OnDestroy } from '@angular/core';
-import { ListItemDirective } from './list-item.directive';
-import * as i0 from "@angular/core";
-/**
- * Accessible list component with keyboard navigation, single- and multi-selection,
- * and flexible delegation of click- and selection-handling to the parent.
- *
- * The component renders as an ARIA `listbox` and delegates keyboard focus tracking
- * to Angular CDK's `ActiveDescendantKeyManager`. Content is projected via
- * `[yuvListItem]`-attributed children (see `ListItemDirective`).
- *
- * **Key Features:**
- * - Single and multi-selection (with Shift / Ctrl modifier support)
- * - Full keyboard navigation (Arrow keys, Space, Enter, Escape)
- * - Horizontal and vertical layout via the `horizontal` host attribute
- * - Auto-selection on initialization via the `autoSelect` input
- * - Selection guarding via `preventChangeUntil` callback
- * - Optional delegation of click and selection handling to the parent component
- * - Accessible: `role="listbox"`, active-descendant focus management, `aria-selected` on items
- *
- * **Basic usage:**
- * ```html
- * <yuv-list (itemSelect)="onItemSelect($event)">
- *   <div yuvListItem>Entry #1</div>
- *   <div yuvListItem>Entry #2</div>
- * </yuv-list>
- * ```
- *
- * **Multi-selection with Shift/Ctrl:**
- * ```html
- * <yuv-list [multiselect]="true" (itemSelect)="onSelect($event)">
- *   @for (item of items; track item.id) {
- *     <div yuvListItem>{{ item.label }}</div>
- *   }
- * </yuv-list>
- * ```
- *
- * **Host Attributes (set declaratively in the template):**
- * - `selectOnEnter` — treat the Enter key as a selection trigger (in addition to Space)
- * - `horizontal` — switch key navigation to left/right arrows instead of up/down
- *
- * @example
- * ```html
- * <!-- Horizontal list, Enter key selects -->
- * <yuv-list horizontal selectOnEnter (itemSelect)="onSelect($event)">
- *   <button yuvListItem>A</button>
- *   <button yuvListItem>B</button>
- * </yuv-list>
- * ```
- */
-export declare class ListComponent implements OnDestroy {
-    #private;
-    /**
-     * All `[yuvListItem]` children projected into this list.
-     *
-     * Queried reactively via `contentChildren` — every time the projected content
-     * changes (items added, removed, or reordered), the `#itemsEffect` re-runs,
-     * rebuilds the key manager, and re-attaches click handlers.
-     */
-    items: import("@angular/core").Signal<readonly ListItemDirective[]>;
-    /**
-     * Guard function that temporarily blocks all selection changes.
-     *
-     * Provide a factory that returns a predicate; as long as that predicate
-     * returns `true`, any attempt to change the selection (via click, keyboard,
-     * or programmatic API) is silently ignored. Useful when the parent has
-     * unsaved changes tied to the current selection and needs to prevent the user
-     * from accidentally navigating away.
-     *
-     * @example
-     * ```ts
-     * // Block selection while a save is in progress
-     * preventChangeUntil = () => () => this.isSaving();
-     * ```
-     *
-     * @default () => false  (never prevents)
-     */
-    preventChangeUntil: import("@angular/core").InputSignal<() => boolean>;
-    /**
-     * Enables multi-selection mode.
-     *
-     * When `true`, the user can hold **Shift** to range-select items between the last
-     * selected item and the clicked one, or hold **Ctrl** to toggle individual items
-     * in and out of the selection. The programmatic `multiSelect()` method is also
-     * only effective when this input is `true`.
-     *
-     * @default false
-     */
-    multiselect: import("@angular/core").InputSignal<boolean>;
-    /**
-     * Delegates visual selection and focus state rendering to the parent component.
-     *
-     * When `false` (default), `yuv-list` applies `.selected` and `.active` CSS classes
-     * to items via `ListItemDirective` signals, so the list stylesheet controls the look.
-     * When `true`, those signals are still updated but the host gets the
-     * `self-handle-selection` CSS class, which the parent can use to opt into its own
-     * visual treatment — useful when item templates have custom selected/focused styling.
-     *
-     * @default false
-     */
-    selfHandleSelection: import("@angular/core").InputSignal<boolean>;
-    /**
-     * Disables the built-in click-to-select behavior, letting the parent component
-     * decide when `select()` is called.
-     *
-     * By default the list attaches an `onClick` handler to every `ListItemDirective`
-     * that calls `select()` with the correct Shift/Ctrl modifier flags. Set this
-     * input to `true` to suppress that wiring — the parent must then call `select()`
-     * imperatively in response to whatever interaction it chooses (e.g. a single-click
-     * that is distinguished from a double-click by `ClickDoubleDirective`).
-     *
-     * @default false
-     */
-    selfHandleClick: import("@angular/core").InputSignal<boolean>;
-    /**
-     * Automatically selects an item when the list is first rendered.
-     *
-     * The selection logic runs once per content-children change (see `#itemsEffect`)
-     * and follows this priority order:
-     * 1. The first non-disabled item that already carries the `selected` attribute.
-     * 2. If no such item exists and `autoSelect` is `true`, the item at index 0.
-     *
-     * Accepts any truthy string value in addition to a real boolean because the
-     * input is also consumable as a plain HTML attribute (`<yuv-list autoSelect>`).
-     *
-     * @default false
-     */
-    autoSelect: import("@angular/core").InputSignalWithTransform<boolean, BooleanInput>;
-    /**
-     * Emits the current selection as an array of zero-based item indices whenever
-     * the selection changes — via click, keyboard, or programmatic API calls.
-     *
-     * An empty array signals that the selection has been cleared.
-     *
-     * @example
-     * ```ts
-     * onItemSelect(indices: number[]): void {
-     *   this.selectedItems = indices.map(i => this.items[i]);
-     * }
-     * ```
-     */
-    itemSelect: import("@angular/core").OutputEmitterRef<number[]>;
-    /**
-     * Emits the zero-based index of the item that received keyboard focus
-     * (i.e. the active descendant managed by `ActiveDescendantKeyManager`).
-     *
-     * Note that focus and selection are independent: navigating with arrow keys
-     * moves focus without changing the selection until Space (or Enter when
-     * `selectOnEnter` is set) is pressed.
-     */
-    itemFocus: import("@angular/core").OutputEmitterRef<number>;
-    /**
-     * Puts the list into a display-only mode where no item can be selected.
-     *
-     * When `true`, all selection paths are blocked: clicks, keyboard shortcuts
-     * (`Space`, `Enter`, `Escape`), and programmatic calls to `select()`,
-     * `multiSelect()`, and `clear()` are all no-ops. The list still renders
-     * normally and keyboard navigation still moves the focus indicator.
-     *
-     * @default false
-     */
-    disableSelection: import("@angular/core").InputSignal<boolean>;
-    /**
-     * When `true`, pressing **Enter** triggers item selection in addition to **Space**.
-     *
-     * Resolved once at construction time from the static `selectOnEnter` host attribute.
-     * Useful in contexts where Enter has a conventional "confirm" meaning (e.g. search
-     * result lists, command palettes).
-     *
-     * Set declaratively in the template: `<yuv-list selectOnEnter>`.
-     */
-    selectOnEnter: boolean;
-    /**
-     * When `true`, switches the `ActiveDescendantKeyManager` to horizontal mode so that
-     * the **Left** / **Right** arrow keys navigate between items instead of **Up** / **Down**.
-     *
-     * Resolved once at construction time from the static `horizontal` host attribute.
-     * The text direction of the document is respected automatically (RTL-aware via CDK
-     * `Directionality`).
-     *
-     * Set declaratively in the template: `<yuv-list horizontal>`.
-     */
-    horizontal: boolean;
-    constructor();
-    ngOnDestroy(): void;
-    /**
-     * Moves keyboard focus to the item at the given index and selects it.
-     *
-     * Combines three operations in one call: updating the CDK key manager's active
-     * descendant (which drives the ARIA active-descendant attribute and the visual focus ring),
-     * selecting the item, and transferring DOM focus to the list host element so that
-     * subsequent keyboard events are processed correctly.
-     *
-     * Safe to call before the key manager is initialized — the guard at the top of
-     * the method prevents errors during early lifecycle phases.
-     *
-     * @param index Zero-based index of the item to activate.
-     */
-    setActiveItem(index: number): void;
-    /**
-     * Transfers DOM focus to the list host element.
-     *
-     * Calling this ensures that subsequent keyboard events (arrow keys, Space, etc.)
-     * are routed to the list's `(keydown)` handler. Called internally by
-     * `setActiveItem()`, but also useful from the parent when programmatic focus
-     * management is needed (e.g. after closing a dialog that was triggered from a
-     * list item).
-     */
-    focus(): void;
-    /**
-     * Smoothly scrolls the list container back to the top.
-     *
-     * Useful after programmatically refreshing the list contents when the user may
-     * have scrolled far down and the new result set should be shown from the beginning.
-     */
-    scrollToTop(): void;
-    /**
-     * Shifts all selected and focused item indices by the given offset.
-     *
-     * Use this when items are prepended or inserted at the beginning of the list so
-     * that the existing selection and keyboard-focus position stay attached to the
-     * same logical items after the index space shifts. A positive offset moves
-     * indices forward (items were inserted before the selection); a negative offset
-     * moves them backward (items were removed before the selection).
-     *
-     * Does **not** emit `itemSelect` — the selection indices change structurally,
-     * not because the user chose different items.
-     *
-     * @param offset Number of positions to shift every selected index by.
-     */
-    shiftSelectionBy(offset: number): void;
-    /**
-     * Programmatically replaces the entire selection with the given indices.
-     *
-     * Only effective when `multiselect` is `true` and `disableSelection` is `false`.
-     * Out-of-range indices are silently discarded. The resulting selection is sorted
-     * ascending before being applied and emitted.
-     *
-     * Use this when the parent needs to restore a previously saved multi-selection
-     * state, e.g. after navigation or on component re-initialization.
-     *
-     * @param index Array of zero-based item indices to select.
-     */
-    multiSelect(index: number[]): void;
-    /**
-     * Selects the item at the given index, optionally extending or toggling
-     * the existing selection using modifier-key semantics.
-     *
-     * - **No modifiers** (default): replaces the current selection with the single item.
-     * - **`shiftKey = true`** (`multiselect` only): range-selects all items between the
-     *   last selected index and `index` (inclusive of neither endpoint, matching typical
-     *   OS list behavior).
-     * - **`ctrlKey = true`** (`multiselect` only): toggles `index` in the selection
-     *   without affecting the rest.
-     *
-     * Index is clamped to `[0, items.length - 1]`. Negative values and calls while
-     * `disableSelection` is `true` are ignored. The `preventChangeUntil` guard is
-     * also respected.
-     *
-     * Emits `itemSelect` after updating the visual state.
-     *
-     * @param index    Zero-based index of the item to select.
-     * @param shiftKey Extend the selection from the last selected item to `index`.
-     * @param ctrlKey  Toggle `index` in or out of the current selection.
-     */
-    select(index: number, shiftKey?: boolean, ctrlKey?: boolean): void;
-    /**
-     * Clears the current selection and resets the active keyboard-focus index.
-     *
-     * If the selection is already empty, the method is a no-op (no event emitted,
-     * no state update). The `preventChangeUntil` guard is respected — if the guard
-     * returns `true`, the clear is blocked entirely.
-     *
-     * Also triggered internally when the user presses **Escape**.
-     *
-     * @param silent When `true`, skips emitting `itemSelect` after clearing. Use this
-     *               when the parent needs to reset state programmatically without
-     *               triggering downstream reactions.
-     */
-    clear(silent?: boolean): void;
-    /**
-     * Host `keydown` handler — routes keyboard events to selection or navigation logic.
-     *
-     * Handled keys:
-     * - **Escape**: clears the selection.
-     * - **Space** (always) / **Enter** (when `selectOnEnter` is set): selects the
-     *   currently focused item. `preventDefault()` is called to stop the browser
-     *   from scrolling the container when Space is pressed.
-     * - **All other keys**: forwarded to `ActiveDescendantKeyManager` so arrow keys,
-     *   Home, End, etc. move the focus indicator without changing the selection.
-     *
-     * When `disableSelection` is `true`, only navigation keys are forwarded to the
-     * key manager — selection keys (Space, Enter, Escape) are suppressed.
-     *
-     * Bound via the `host` metadata as `(keydown)`.
-     *
-     * @param event The keyboard event originating from the list host element.
-     */
-    protected onKeydown(event: KeyboardEvent): void;
-    /**
-     * Host `focus` handler — restores a sensible focus position when the list
-     * host element receives DOM focus without an item already being active.
-     *
-     * The logic runs inside a 300 ms timeout so that focus events triggered by
-     * an item being clicked (which also bubbles a focus event up to the host)
-     * have already resolved their own active-item state before this handler acts.
-     * If an active item already exists when the timeout fires, nothing happens.
-     *
-     * Focus target priority:
-     * 1. The first index in the current selection (so the user lands back on the
-     *    previously selected item when tabbing into the list).
-     * 2. Index 0 as the fallback when there is no selection.
-     *
-     * Bound via the `host` metadata as `(focus)`.
-     */
-    protected onFocus(): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<ListComponent, never>;
-    static ɵcmp: i0.ɵɵComponentDeclaration<ListComponent, "yuv-list", never, { "preventChangeUntil": { "alias": "preventChangeUntil"; "required": false; "isSignal": true; }; "multiselect": { "alias": "multiselect"; "required": false; "isSignal": true; }; "selfHandleSelection": { "alias": "selfHandleSelection"; "required": false; "isSignal": true; }; "selfHandleClick": { "alias": "selfHandleClick"; "required": false; "isSignal": true; }; "autoSelect": { "alias": "autoSelect"; "required": false; "isSignal": true; }; "disableSelection": { "alias": "disableSelection"; "required": false; "isSignal": true; }; }, { "itemSelect": "itemSelect"; "itemFocus": "itemFocus"; }, ["items"], ["*"], true, never>;
-}

package/list/lib/list.module.d.ts

@@ -1,9 +0,0 @@
-import * as i0 from "@angular/core";
-import * as i1 from "./list.component";
-import * as i2 from "./list-item.directive";
-import * as i3 from "./list-tile/list-tile.component";
-export declare class YuvListModule {
-    static ɵfac: i0.ɵɵFactoryDeclaration<YuvListModule, never>;
-    static ɵmod: i0.ɵɵNgModuleDeclaration<YuvListModule, never, [typeof i1.ListComponent, typeof i2.ListItemDirective, typeof i3.ListTileComponent], [typeof i1.ListComponent, typeof i2.ListItemDirective, typeof i3.ListTileComponent]>;
-    static ɵinj: i0.ɵɵInjectorDeclaration<YuvListModule>;
-}

package/master-details/lib/master-details.component.d.ts

@@ -1,52 +0,0 @@
-import { AfterViewInit, TemplateRef } from '@angular/core';
-import { MasterDetailsLayoutOptions } from './master-details.interface';
-import * as i0 from "@angular/core";
-/**
- * Component rendering a master/details view.
- *
- * @example
- * <yuv-master-details [(detailsActive)]="detailsActive">
- *   <ng-template #yuvMasterPane>Main Pane</ng-template>
- *   <ng-template #yuvDetailsPane>Details Pane</ng-template>
- * </yuv-master-details>
- */
-export declare class YuvMasterDetailsComponent implements AfterViewInit {
-    #private;
-    masterPane: import("@angular/core").Signal<TemplateRef<any>>;
-    detailsPane: import("@angular/core").Signal<TemplateRef<any>>;
-    detailsPaneTplateRef: import("@angular/core").Signal<TemplateRef<any>>;
-    private _defaultLayoutOptions;
-    /**
-     * Enable/disable details pane (also use as two-way-bound variable: [(detailsActive)])
-     */
-    detailsActive: import("@angular/core").ModelSignal<boolean>;
-    smallScreenLayout: import("@angular/core").WritableSignal<boolean>;
-    /**
-     * Layout settings is the state of the master details that could be persisted.
-     * Setting a `layoutSettingsID` will save the current state (details area visibilkity and
-     * split area sizes etc.) to the local storage. If the component is created, it will load
-     * those settings and re-apply them.
-     */
-    layoutSettingsID?: string;
-    private _layoutOptions;
-    /**
-     * Layout options to be applied.
-     */
-    set layoutOptions(lo: Partial<MasterDetailsLayoutOptions>);
-    get layoutOptions(): MasterDetailsLayoutOptions;
-    undockableDetails: import("@angular/core").InputSignal<boolean>;
-    /**
-     * Styles tp be applied to the panels
-     */
-    panelStyle: import("@angular/core").InputSignal<{
-        [key: string]: string;
-    } | undefined>;
-    /**
-     * Size of the gutter in Pixel.
-     */
-    gutterSize: import("@angular/core").InputSignal<number | undefined>;
-    onPopIn(): void;
-    ngAfterViewInit(): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<YuvMasterDetailsComponent, never>;
-    static ɵcmp: i0.ɵɵComponentDeclaration<YuvMasterDetailsComponent, "yuv-master-details", never, { "detailsActive": { "alias": "detailsActive"; "required": false; "isSignal": true; }; "layoutSettingsID": { "alias": "layoutSettingsID"; "required": false; }; "layoutOptions": { "alias": "layoutOptions"; "required": false; }; "undockableDetails": { "alias": "undockableDetails"; "required": false; "isSignal": true; }; "panelStyle": { "alias": "panelStyle"; "required": false; "isSignal": true; }; "gutterSize": { "alias": "gutterSize"; "required": false; "isSignal": true; }; }, { "detailsActive": "detailsActiveChange"; }, ["masterPane", "detailsPane"], never, true, never>;
-}

package/master-details/lib/master-details.interface.d.ts

@@ -1,7 +0,0 @@
-export interface MasterDetailsLayoutOptions {
-    masterSize?: number;
-    masterMinSize?: number;
-    detailsSize?: number;
-    detailsMinSize?: number;
-    resizable: boolean;
-}

package/master-details/lib/master-details.module.d.ts

@@ -1,7 +0,0 @@
-import * as i0 from "@angular/core";
-import * as i1 from "./master-details.component";
-export declare class YuvMasterDetailsModule {
-    static ɵfac: i0.ɵɵFactoryDeclaration<YuvMasterDetailsModule, never>;
-    static ɵmod: i0.ɵɵNgModuleDeclaration<YuvMasterDetailsModule, never, [typeof i1.YuvMasterDetailsComponent], [typeof i1.YuvMasterDetailsComponent]>;
-    static ɵinj: i0.ɵɵInjectorDeclaration<YuvMasterDetailsModule>;
-}

package/metadata-form/lib/metadata-form-element-registry.service.d.ts

@@ -1,60 +0,0 @@
-import { TemplateRef } from '@angular/core';
-import { Situation } from '@yuuvis/client-core';
-import * as i0 from "@angular/core";
-/**
- * Object forms are used to render and edit metadata of DMS objects. Each property
- * of an object can be rendered in a diffenrent way, depending on the type of the property.
- * This service allows to register and retrieve templates for rendering these form elements.
- *
- * You can register templates for different situations like EDIT, SEARCH, and CREATE.
- * The templates will then be used to render the form elements in the object form component.
- *
- * So based on the property type you can register custom templates for rendering certain
- * form elements. This is useful if you want to render a property in a different way.
- *
- * Example:
- * Having a number property representing a rating, you might want to render it as
- * a list of stars instead of a simple input field.
- */
-export declare class MetadataFormElementRegistry {
-    private _defaults;
-    private _edit;
-    private _search;
-    private _create;
-    NAME_PROPERTY_PREFIX: string;
-    /**
-     * Get a template to render a certain form element
-     * @param propertyType The internal type to get the template for
-     * @param situation Form situation
-     * @returns TemplateRef or undefined
-     */
-    getElementTemplate(propertyType: string, situation?: string): TemplateRef<any> | undefined;
-    /**
-     * Register an object form element for a certain internal type. You might add a new component
-     * or overwrite an existung one.
-     * @param propertyType The internal type to provide the component for
-     * @param component The component
-     * @param situation Form situation to provide thew form element for (defaults to EDIT)
-     */
-    addElementTemplate(propertyType: string, templateRef: TemplateRef<any>, situation?: Situation): void;
-    /**
-     * Remove a registered form element.
-     * @param propertyType The internal type to remove the component for
-     * @param situation Form situation to provide thew form element for (defaults to EDIT)
-     */
-    removeElementTemplate(propertyType: string, situation?: Situation): void;
-    /**
-     * Register default form element component. Usually this will be done by the object
-     * form component itself.
-     * @param propertyType The internal type to provide the component for
-     * @param component The default component
-     */
-    _addDefaultElementTemplate(propertyType: string, templateRef: TemplateRef<any>): void;
-    /**
-     * Remove a registered default form element.
-     * @param propertyType The internal type to remove the component for
-     */
-    _removeDefaultElementTemplate(propertyType: string): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<MetadataFormElementRegistry, never>;
-    static ɵprov: i0.ɵɵInjectableDeclaration<MetadataFormElementRegistry>;
-}

package/metadata-form/lib/metadata-form-field/metadata-form-field.component.d.ts

@@ -1,25 +0,0 @@
-import { TemplateRef } from '@angular/core';
-import { ObjectTypeField } from '@yuuvis/client-core';
-import { Subject } from 'rxjs';
-import { MetadataFormFieldContext, ParentFormChangedEvent } from './metadata-form-field.interface';
-import * as i0 from "@angular/core";
-import * as i1 from "@yuuvis/client-framework/common";
-/**
- * Component to render a metadata form field within an object form. These forms are
- * created to render and edit metadata of DMS objects. This component is used as a wrapper
- * for the actual form element, which is defined by the `formField` input.
- */
-export declare class MetadataFormFieldComponent {
-    #private;
-    readonly: boolean;
-    formChangedSubject: import("@angular/core").InputSignal<Subject<ParentFormChangedEvent> | undefined>;
-    formField: import("@angular/core").InputSignal<ObjectTypeField>;
-    elementTemplate: import("@angular/core").Signal<TemplateRef<any> | undefined>;
-    context: import("@angular/core").Signal<MetadataFormFieldContext>;
-    /**
-     * Form situation, if not set default will be 'EDIT'
-     */
-    situation: import("@angular/core").InputSignal<string | undefined>;
-    static ɵfac: i0.ɵɵFactoryDeclaration<MetadataFormFieldComponent, never>;
-    static ɵcmp: i0.ɵɵComponentDeclaration<MetadataFormFieldComponent, "yuv-metadata-form-field", never, { "formChangedSubject": { "alias": "formChangedSubject"; "required": false; "isSignal": true; }; "formField": { "alias": "field"; "required": true; "isSignal": true; }; "situation": { "alias": "situation"; "required": false; "isSignal": true; }; }, {}, never, never, true, [{ directive: typeof i1.NoopValueAccessorDirective; inputs: {}; outputs: {}; }]>;
-}

package/metadata-form/lib/metadata-form-field/metadata-form-field.interface.d.ts

@@ -1,19 +0,0 @@
-import { AbstractControl } from '@angular/forms';
-import { ObjectTypeField } from '@yuuvis/client-core';
-import { Subject } from 'rxjs';
-/**
- * Context provided to each metadata form field.
- */
-export interface MetadataFormFieldContext {
-    label?: string;
-    situation: string;
-    field: ObjectTypeField;
-    ctrl?: AbstractControl<any, any>;
-    formChangedSubject?: Subject<ParentFormChangedEvent>;
-}
-export interface ParentFormChangedEvent {
-    invalid: boolean;
-    dirty: boolean;
-    indexdataChanged: boolean;
-    data?: any;
-}

package/metadata-form/lib/object-metadata-element-error.directive.d.ts

@@ -1,17 +0,0 @@
-import { OnInit } from '@angular/core';
-import { ObjectFormControl } from '@yuuvis/client-core';
-import * as i0 from "@angular/core";
-/**
- * Directive to apply an object-form related error to as inner text to an element.
- * This could be used to render objec tform related errors in a custom element like <mat-error>.
- *
- * @example
- * <mat-error [yuvObjectMetadataElementError]="myControl"></mat-error>
- */
-export declare class ObjectMetadataElementErrorDirective implements OnInit {
-    #private;
-    yuvObjectMetadataElementError: import("@angular/core").InputSignal<ObjectFormControl | undefined>;
-    ngOnInit(): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<ObjectMetadataElementErrorDirective, never>;
-    static ɵdir: i0.ɵɵDirectiveDeclaration<ObjectMetadataElementErrorDirective, "[yuvObjectMetadataElementError]", never, { "yuvObjectMetadataElementError": { "alias": "yuvObjectMetadataElementError"; "required": false; "isSignal": true; }; }, {}, never, never, true, never>;
-}

package/metadata-form/lib/object-metadata-element-label.directive.d.ts

@@ -1,29 +0,0 @@
-import { AfterViewInit, OnInit } from '@angular/core';
-import { MetadataFormFieldContext } from './metadata-form-field/metadata-form-field.interface';
-import * as i0 from "@angular/core";
-/**
- * Directive to apply styles to an object metadata element label based on its control status.
- * Depending on the state of the control (dirty, error, required), it will add or remove specific classes
- * to the label element. These classes could then be used to style the label accordingly.
- *
- * Could be placed on any HTML element, but is primarily intended for use on `<mat-label>` or `<label>` elements.
- * If you would like to use it on any other element, make sure to add the class 'label' to it.
- *
- * @example
- * <mat-label [yuvObjectMetadataElementLabel]="ctx">My Label</mat-label>
- * <label [yuvObjectMetadataElementLabel]="ctx">My Label</label>
- * <div class="label" [yuvObjectMetadataElementLabel]="ctx">My Label</div>
- */
-export declare class ObjectMetadataElementLabelDirective implements OnInit, AfterViewInit {
-    #private;
-    state: import("@angular/core").WritableSignal<{
-        dirty: boolean;
-        required: boolean;
-        invalid: boolean;
-    }>;
-    yuvObjectMetadataElementLabel: import("@angular/core").InputSignal<MetadataFormFieldContext | undefined>;
-    ngOnInit(): void;
-    ngAfterViewInit(): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<ObjectMetadataElementLabelDirective, never>;
-    static ɵdir: i0.ɵɵDirectiveDeclaration<ObjectMetadataElementLabelDirective, "[yuvObjectMetadataElementLabel]", never, { "yuvObjectMetadataElementLabel": { "alias": "yuvObjectMetadataElementLabel"; "required": false; "isSignal": true; }; }, {}, never, never, true, never>;
-}

package/metadata-form/lib/object-metadata-element-template.directive.d.ts

@@ -1,45 +0,0 @@
-import { OnDestroy, OnInit } from '@angular/core';
-import { Situation } from '@yuuvis/client-core';
-import * as i0 from "@angular/core";
-/**
- * Directive to be applied to a `ng-template`. It will register the template as a
- * form element used by object-form component.
- *
- * Context is provided with the following fields:
- * - situation: form situation 'EDIT', 'CREATE', 'SEARCH'
- * - field: ObjectTypeField
- * - ngControl: Reactive FormControl
- *
- * @example
- * <ng-template yuvMetadataElementTemplate propertyType="boolean:switch" let-ctx>...</ng-template>
- *
- */
-export declare class ObjectMetadataElementTemplateDirective implements OnInit, OnDestroy {
-    #private;
-    /**
-     * Bucket to register the template. Use 'default' for templates that should be
-     * used across all situations.
-     */
-    yuvMetadataElementTemplate: import("@angular/core").InputSignal<string | undefined>;
-    /**
-     * Situation to register the template for. So only object forms for that
-     * situation (CREATE, EDIT, SEARCH) will use the template. Defaults to `EDIT`.
-     */
-    situation: import("@angular/core").InputSignal<Situation>;
-    /**
-     * Internal property type to get the registered template. You need to set either
-     * `propertyType` or `propertyName` to get a template. Setting a name and
-     * a type, the name will be used because it is more precise.
-     */
-    propertyType: import("@angular/core").InputSignal<string | undefined>;
-    /**
-     * Pick registered metadata element by name. You need to set either
-     * `propertyType` or `propertyName` to get a template. Setting a name and
-     * a type, the name will be used because it is more precise.
-     */
-    propertyName: import("@angular/core").InputSignal<string | undefined>;
-    ngOnInit(): void;
-    ngOnDestroy(): void;
-    static ɵfac: i0.ɵɵFactoryDeclaration<ObjectMetadataElementTemplateDirective, never>;
-    static ɵdir: i0.ɵɵDirectiveDeclaration<ObjectMetadataElementTemplateDirective, "[yuvMetadataElementTemplate]", never, { "yuvMetadataElementTemplate": { "alias": "yuvMetadataElementTemplate"; "required": false; "isSignal": true; }; "situation": { "alias": "situation"; "required": false; "isSignal": true; }; "propertyType": { "alias": "propertyType"; "required": false; "isSignal": true; }; "propertyName": { "alias": "propertyName"; "required": false; "isSignal": true; }; }, {}, never, never, true, never>;
-}

package/metadata-form-defaults/lib/metadata-default-templates/metadata-default-templates.component.d.ts

@@ -1,5 +0,0 @@
-import * as i0 from "@angular/core";
-export declare class MetadataDefaultTemplatesComponent {
-    static ɵfac: i0.ɵɵFactoryDeclaration<MetadataDefaultTemplatesComponent, never>;
-    static ɵcmp: i0.ɵɵComponentDeclaration<MetadataDefaultTemplatesComponent, "yuv-metadata-default-templates", never, {}, {}, never, never, true, never>;
-}

package/metadata-form-defaults/lib/metadata-form-defaults.module.d.ts

@@ -1,7 +0,0 @@
-import * as i0 from "@angular/core";
-import * as i1 from "./metadata-default-templates/metadata-default-templates.component";
-export declare class YuvMetadataFormDefaultsModule {
-    static ɵfac: i0.ɵɵFactoryDeclaration<YuvMetadataFormDefaultsModule, never>;
-    static ɵmod: i0.ɵɵNgModuleDeclaration<YuvMetadataFormDefaultsModule, never, [typeof i1.MetadataDefaultTemplatesComponent], [typeof i1.MetadataDefaultTemplatesComponent]>;
-    static ɵinj: i0.ɵɵInjectorDeclaration<YuvMetadataFormDefaultsModule>;
-}