@yuuvis/client-framework 3.17.1 → 3.18.0

package/lib/assets/i18n/de.json

@@ -92,6 +92,7 @@
   "yuv.object-metadata.tabs.indexdata.title": "Metadaten",
   "yuv.object-flavor.apply-flavor.button.apply": "Anwenden",
   "yuv.object-flavor.apply-flavor.button.cancel": "Abbrechen",
+  "yuv.object-flavor.apply-flavor.error": "Der Typ konnte nicht hinzugefügt werden.",
   "yuv.object-flavor.apply-flavor.headline": "Typ '{{name}}' hinzufügen",
   "yuv.object-flavor.button.add": "Typ hinzufügen",
   "yuv.object-flavor.button.clear-selection": "Auswahl aufheben",

package/lib/assets/i18n/en.json

@@ -92,6 +92,7 @@
   "yuv.object-metadata.tabs.indexdata.title": "Metadata",
   "yuv.object-flavor.apply-flavor.button.apply": "Apply",
   "yuv.object-flavor.apply-flavor.button.cancel": "Cancel",
+  "yuv.object-flavor.apply-flavor.error": "The type could not be added.",
   "yuv.object-flavor.apply-flavor.headline": "Add type '{{name}}'",
   "yuv.object-flavor.button.add": "Add type",
   "yuv.object-flavor.button.clear-selection": "Unselect",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yuuvis/client-framework",
-  "version": "3.17.1",
+  "version": "3.18.0",
   "author": "OPTIMAL SYSTEMS GmbH <npm@optimal-systems.de>",
   "license": "MIT",
   "peerDependencies": {
@@ -8,16 +8,16 @@
     "@angular/common": "^21.2.19",
     "@angular/core": "^21.2.19",
     "angular-gridster2": "^21.0.1",
-    "@yuuvis/client-core": "^3.17.1",
-    "@yuuvis/client-shell-core": "^3.17.1",
-    "@yuuvis/client-components": "^3.17.1",
+    "@yuuvis/client-core": "^3.18.0",
+    "@yuuvis/client-shell-core": "^3.18.0",
+    "@yuuvis/client-components": "^3.18.0",
     "ng-dynamic-component": "^10.8.2",
     "modern-normalize": "^3.0.1"
   },
   "dependencies": {
     "@angular/material": "^21.2.14",
     "@ngrx/signals": "^21.1.0",
-    "@yuuvis/material": "^3.17.1",
+    "@yuuvis/material": "^3.18.0",
     "@yuuvis/media-viewer": "^4.0.0",
     "angular-split": "^20.0.0",
     "vis-network": "^10.0.2",

package/types/yuuvis-client-framework-badges.d.ts

@@ -1,6 +1,6 @@
 import * as _angular_core from '@angular/core';
 import { Signal } from '@angular/core';
-import { DmsObject, YuvUser, LockState } from '@yuuvis/client-core';
+import { DmsObject, YuvUser, LockState, VirtualObjectType } from '@yuuvis/client-core';
 import { Severity } from '@yuuvis/material/badge';
 
 type BadgeSeverity = Severity;
@@ -14,6 +14,23 @@ interface BadgeRule {
     op: 'isSet' | 'equals' | 'tagPresent';
     value?: unknown;
 }
+/**
+ * Restricts the object types a badge may be configured for. Mirrors
+ * `ActionSupport`: an entry matches when the object type id is listed in
+ * `types` or `sots`, or matches `pattern`.
+ *
+ * This scopes *configurability* (which types offer the badge in selection UIs
+ * such as the tile config), not rendering — whether a badge actually shows on
+ * a given object stays governed by {@link Badge.applies} / {@link Badge.rule}.
+ */
+interface BadgeSupport {
+    /** Object types the badge can be configured for (e.g. `system:document`). */
+    types?: string[];
+    /** Secondary object types the badge can be configured for. */
+    sots?: string[];
+    /** Pattern matched against the object type id. */
+    pattern?: string;
+}
 interface Badge {
     id: string;
     labelKey: string;
@@ -29,6 +46,12 @@ interface Badge {
      * the id filter. Variants are hidden from selection UIs.
      */
     variantOf?: string;
+    /**
+     * Object types this badge may be configured for. When omitted, the badge is
+     * offered for every type. Variants inherit the support of their parent badge
+     * and are hidden from selection UIs anyway.
+     */
+    supports?: BadgeSupport;
     applies?: (dmsObject: DmsObject, ctx: BadgeContext) => boolean;
     rule?: BadgeRule;
 }
@@ -53,10 +76,15 @@ declare class BadgeSelectComponent {
     #private;
     selectedBadgeIds: _angular_core.InputSignal<string[]>;
     bucket: _angular_core.InputSignal<string | undefined>;
+    /**
+     * Type currently being configured. Badges that declare `supports` are only
+     * offered for the types they support. Omitting it offers every badge.
+     */
+    objectType: _angular_core.InputSignal<VirtualObjectType | undefined>;
     badgeSelect: _angular_core.OutputEmitterRef<Badge>;
     readonly badges: Signal<Badge[]>;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<BadgeSelectComponent, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<BadgeSelectComponent, "yuv-tile-badge-select", never, { "selectedBadgeIds": { "alias": "selectedBadgeIds"; "required": false; "isSignal": true; }; "bucket": { "alias": "bucket"; "required": false; "isSignal": true; }; }, { "badgeSelect": "badgeSelect"; }, never, never, true, never>;
+    static ɵcmp: _angular_core.ɵɵComponentDeclaration<BadgeSelectComponent, "yuv-tile-badge-select", never, { "selectedBadgeIds": { "alias": "selectedBadgeIds"; "required": false; "isSignal": true; }; "bucket": { "alias": "bucket"; "required": false; "isSignal": true; }; "objectType": { "alias": "objectType"; "required": false; "isSignal": true; }; }, { "badgeSelect": "badgeSelect"; }, never, never, true, never>;
 }
 
 /**
@@ -84,6 +112,10 @@ declare const LOCK_SELF_BADGE: Badge;
  * @remarks
  * - `severity` is set to `'danger'` to visually emphasize the retention constraint.
  * - `priority` is `20`, which controls the display order relative to other badges.
+ * - `supports` limits the badge to documents, so selection UIs such as the tile
+ *   config do not offer it for folder types. It only scopes configurability -
+ *   `applies` still governs rendering, so an object under retention keeps its
+ *   badge regardless.
  */ declare const RETENTION_BADGE: Badge;
 
 declare class BadgeRegistryService {
@@ -196,6 +228,21 @@ declare class TileBadgesComponent {
  * @returns `true` if the rule matches; otherwise `false`.
  */
 declare function evaluateRule(rule: BadgeRule, dmsObject: DmsObject): boolean;
+/**
+ * Checks whether a badge may be configured for the given object type.
+ *
+ * A badge without {@link Badge.supports} is unrestricted and matches every
+ * type. Otherwise the type's `objectType` and its `sots` are matched against
+ * the badge's `types` / `sots` lists and its `pattern`; a single hit is enough.
+ *
+ * Called without an object type (no type context available) the badge is kept,
+ * so callers that do not know the type never lose badges.
+ *
+ * @param badge Badge to check.
+ * @param objectType Type the selection UI is currently configuring.
+ * @returns `true` if the badge may be offered for that type; otherwise `false`.
+ */
+declare function badgeSupportsType(badge: Badge, objectType?: VirtualObjectType): boolean;
 
-export { BadgeChipComponent, BadgeRegistryService, BadgeSelectComponent, LOCK_BADGE, LOCK_SELF_BADGE, RETENTION_BADGE, TileBadgesComponent, evaluateRule };
-export type { Badge, BadgeContext, BadgeRule, BadgeSeverity };
+export { BadgeChipComponent, BadgeRegistryService, BadgeSelectComponent, LOCK_BADGE, LOCK_SELF_BADGE, RETENTION_BADGE, TileBadgesComponent, badgeSupportsType, evaluateRule };
+export type { Badge, BadgeContext, BadgeRule, BadgeSeverity, BadgeSupport };