@zambon-dev/library 1.4.1 → 1.6.0

package/lib/components/sidebar/sidebar.component.d.ts

@@ -24,7 +24,16 @@ export declare class SidebarComponent extends BaseComponent implements AfterView
     collapse(): void;
     protected trackByFn(_index: number, item: SidebarMenu): number;
     protected trackByRegion(_index: number, region: SidebarRegion): string;
+    /** Whether this top-level menu stands for an area rather than a destination of its own. */
+    private isArea;
+    private groupByRegionLabel;
+    private groupByRootMenus;
     private groupIntoRegions;
+    /**
+     * Fetches the children of every area up front, because they are rendered flat rather than
+     * behind a click, so the lazy load a collapsible parent relies on would never be triggered.
+     */
+    private loadAreaChildren;
     private deactivate;
     private updateShouldActivate;
     static ɵfac: i0.ɵɵFactoryDeclaration<SidebarComponent, never>;

package/lib/helpers/display-controls.d.ts

@@ -0,0 +1,29 @@
+import { AbstractControl } from '@angular/forms';
+/**
+ * Tracks the form controls that exist only to show a catalog selection's label.
+ *
+ * `lib-catalog-select` works in pairs: the control named by `controlName` holds the identifier, and
+ * the one named by `displayControlName` holds the text the user reads. The second is created by the
+ * component itself when a screen does not declare it, so a form ends up carrying controls nobody
+ * wrote down — and a filters form then submits them alongside the real filters.
+ *
+ * The mark lives in a `WeakSet` keyed by the control instance rather than by its name. That is the
+ * only scope that is actually correct: two forms may each have an `employeeName`, and only the one
+ * a catalog select drives is a display control. It also keeps nothing alive.
+ */
+export declare class DisplayControls {
+    private static readonly marked;
+    /**
+     * Whether the control exists only to display a catalog selection's label.
+     *
+     * @param control The control, which may be absent.
+     * @returns `true` when a catalog select drives it as its display control.
+     */
+    static isDisplayControl(control: AbstractControl | null | undefined): boolean;
+    /**
+     * Marks the control as existing only to display a catalog selection's label.
+     *
+     * @param control The control, which may be absent.
+     */
+    static markAsDisplayControl(control: AbstractControl | null | undefined): void;
+}

package/lib/helpers/index.d.ts

@@ -1,3 +1,4 @@
 export { DateHelpers } from './date-helpers';
+export { DisplayControls } from './display-controls';
 export { GuidHelper } from './guid-helper';
 export { RouterFormatter } from './route-formatter';

package/lib/models/sidebar/sidebar-configs.d.ts

@@ -5,6 +5,17 @@ export declare class SidebarConfigs {
     /** Tooltip for items that open in a new browser tab. Rendered as-is, like {@link errorText}. */
     externalLinkText: string;
     loadingText: string;
+    /**
+     * Derive region headers from the menu tree instead of from {@link SidebarMenu.region}.
+     *
+     * With this on, a top-level menu that has children and no URL stops being a collapsible node
+     * and becomes an area header, with its children rendered flat beneath it as top-level items --
+     * icons included. The area is then a real menu row, so it carries its own translated label and
+     * its own order, and no `region` label has to be repeated across every item that belongs to it.
+     *
+     * Off by default: without it a top-level parent stays the collapsible group it has always been.
+     */
+    shouldDeriveAreasFromRootMenus: boolean;
     logoCollapsedPath?: string;
     logoExpandedPath?: string;
     constructor(options?: Partial<SidebarConfigs>);

package/lib/services/sidebar.service.d.ts

@@ -16,6 +16,12 @@ export declare abstract class SidebarService {
     private selectedMenu;
     deselectAll(): void;
     loadChildren(parentMenu: SidebarMenu): void;
+    /**
+     * Loads a parent's children and hands them back, for callers that need them before the user
+     * clicks -- a sidebar rendering areas flat has to have them up front. {@link loadChildren} is
+     * the fire-and-forget variant that also raises the loading and failure events.
+     */
+    loadChildrenFor(parentMenu: SidebarMenu): Observable<SidebarMenu[]>;
     loadRoot(): Observable<SidebarMenu[]>;
     select(menu: SidebarMenu): void;
     private deselectMenu;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zambon-dev/library",
-  "version": "1.4.1",
+  "version": "1.6.0",
   "description": "Angular UI components and shared presentation utilities for Zambon applications.",
   "keywords": [
     "angular",