commons-shared-web-ui 0.0.68 → 0.0.70

package/index.d.ts

@@ -372,6 +372,16 @@ interface DateConfig {
     inputReadonly?: boolean;
     /** Name of a sibling field whose value is used as the dynamic minimum date. */
     minDateField?: string;
+    /**
+     * Fixes this field's picker to a specific entry granularity — no per-user toggle.
+     * 'DAY' (default, or omitted) = today's full day+month+year picker, unchanged.
+     * 'MONTH' = the picker opens straight to the year grid; picking a month commits that
+     *   month with day=1 and closes immediately (the day grid is never shown).
+     * 'YEAR' = the picker opens to the year grid; picking a year commits Jan 1 of that year
+     *   and closes immediately (neither the month nor day grid is ever shown).
+     * Opt-in and additive: fields that don't set this keep today's default behavior.
+     */
+    dateGranularity?: 'DAY' | 'MONTH' | 'YEAR';
 }
 interface TimeConfig {
     /** Explicit minimum time in "HH:mm" 24-hour format (e.g. "09:00"). */
@@ -1539,6 +1549,46 @@ declare class FormFieldComponent implements OnInit, AfterViewInit, OnDestroy {
     get effectiveMinTime(): string | null;
     /** Effective maximum time for the time input (explicit maxTime only). */
     get effectiveMaxTime(): string | null;
+    /** Fixed entry granularity for this DATE field — no per-user toggle, set entirely by
+     *  config (see DateConfig.dateGranularity's doc for what each level means). */
+    get effectiveDateGranularity(): 'DAY' | 'MONTH' | 'YEAR';
+    /** Effective start view for the datepicker — jumps straight to the year grid for
+     *  MONTH/YEAR granularity so the day grid (and, for YEAR, the month grid) is skipped. */
+    get datePickerStartView(): 'month' | 'year' | 'multi-year';
+    /**
+     * Material's (yearSelected) output on <mat-datepicker> — fires whenever a year is
+     * clicked in the multi-year grid, for ANY granularity (it's just how Material's
+     * datepicker works), so this only acts when granularity is actually 'YEAR': commits
+     * Jan 1 of that year and closes immediately, skipping the month/day grids entirely.
+     * For 'DAY'/'MONTH' granularity this is a no-op — Material's own default behavior
+     * (drill into the month grid next) proceeds untouched.
+     */
+    onDateYearSelected(date: Date, picker: {
+        close: () => void;
+    }): void;
+    /**
+     * Material's (monthSelected) output — fires when a month is clicked in the month grid.
+     * Only acts when granularity is 'MONTH': commits day=1 for that month/year and closes
+     * immediately, skipping the day grid. No-op for 'DAY' (default drill-in continues) and
+     * 'YEAR' (the picker already closed at year-selection, so this never fires for YEAR).
+     */
+    onDateMonthSelected(date: Date, picker: {
+        close: () => void;
+    }): void;
+    /**
+     * Fired every time the picker opens (Material's (opened) output). `startView` only sets
+     * the calendar's view on its very first render — clicking a year (in multi-year view)
+     * also drives Material's OWN internal auto-drill (MatCalendar's `_goToDateInView`, called
+     * as a side effect of the exact same click that fires (yearSelected)/(monthSelected)),
+     * which advances the calendar's `currentView` to 'year' then 'month' regardless of our
+     * close()-on-select handlers above. There's no public API to suppress that internal
+     * drill, so for MONTH/YEAR granularity we defensively force the view back to
+     * 'multi-year' on every open via Material's internal calendar reference — there's no
+     * supported public way to do this, so it's wrapped in a try/catch and silently no-ops if
+     * that internal shape ever changes in a future Material version. No-op entirely for
+     * 'DAY' granularity, leaving default date fields completely untouched.
+     */
+    onDatePickerOpened(picker: any): void;
     isMultiDropdownOpen: boolean;
     isSingleDropdownOpen: boolean;
     dropdownCurrentPage: number;
@@ -4515,6 +4565,12 @@ interface FilterPanelConfig {
     smartFormConfig: FormSchema;
     /** Maps each form field to the API query-param that the table expects */
     filterParamMapping: FilterParamMap[];
+    /**
+     * Controls whether filter parameters are appended as URL query parameters ('queryParams')
+     * or merged into tableConfig.apiPayload ('apiPayload').
+     * Default: 'queryParams' for GET, 'apiPayload' for POST.
+     */
+    filterTarget?: 'queryParams' | 'apiPayload';
     /**
      * Optional default values pre-filled when the component opens AND restored on Clear Filter.
      * Key = formFieldName, Value = the field value.
@@ -4642,8 +4698,9 @@ declare class FilterTableSelectorComponent implements OnInit, OnChanges, OnDestr
      */
     private buildFormJson;
     /**
-     * Rebuilds resolvedTableConfig with the current activeFilterParams appended
-     * to the base API URL.
+     * Rebuilds resolvedTableConfig.
+     * If filterTarget is 'apiPayload' (or tableConfig.apiMethod is 'POST'), filter parameters are merged into apiPayload.
+     * Otherwise, filter parameters are appended to apiUrl as query string parameters.
      */
     private applyFilterParamsToTable;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "commons-shared-web-ui",
-  "version": "0.0.68",
+  "version": "0.0.70",
   "peerDependencies": {
     "@angular/animations": "20.3.15",
     "@angular/cdk": "20.2.14",