@cdevhub/ngx-tw 0.6.1 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cdevhub/ngx-tw",
-  "version": "0.6.1",
+  "version": "0.7.0",
   "description": "Angular component library for Tailwind CSS v4 — accessible, signal-based, built on Angular CDK.",
   "keywords": [
     "angular",

package/types/cdevhub-ngx-tw-tabs.d.ts

@@ -22,8 +22,28 @@ declare class TabComponent {
     readonly label: _angular_core.InputSignal<string>;
     /** When true, the tab cannot be selected and is skipped by keyboard navigation. Defaults to false. */
     readonly disabled: _angular_core.InputSignal<boolean>;
-    /** When true, a dismiss control is rendered in the tab trigger. The control is pointer-only; the keyboard gesture is Delete on the focused tab. Defaults to false. */
-    readonly closable: _angular_core.InputSignal<boolean>;
+    /**
+     * When true, a dismiss control is rendered in the tab trigger. The control is pointer-only; the keyboard gesture is Delete on the focused tab. Defaults to false.
+     *
+     * @deprecated Bind `dismissible` instead. `closable` was the library's only
+     * spelling of this concept — `alert`, `badge` and `toast` all call it
+     * `dismissible` — and one idea should not have two names. Both work; `closable`
+     * is removed in the next major.
+     */
+    readonly closable: _angular_core.InputSignalWithTransform<boolean, unknown>;
+    /**
+     * When true, a dismiss control is rendered in the tab trigger. The control is pointer-only; the keyboard gesture is Delete on the focused tab. Defaults to false.
+     *
+     * Canonical spelling, matching `alert`, `badge` and `toast`. Supersedes the
+     * deprecated `closable`; binding either one enables the control.
+     */
+    readonly dismissible: _angular_core.InputSignalWithTransform<boolean, unknown>;
+    /**
+     * @internal Whether a dismiss control should render, from either spelling.
+     * Both inputs default to `false`, so `||` is the correct reconciliation: it is
+     * true exactly when the consumer opted in through one name or the other.
+     */
+    readonly isDismissible: _angular_core.Signal<boolean>;
     /** When true, the tab panel content is only instantiated when the tab becomes active for the first time. Defaults to false. */
     readonly lazy: _angular_core.InputSignal<boolean>;
     /** @internal Custom trigger template, if provided. */
@@ -33,7 +53,7 @@ declare class TabComponent {
     /** @internal Implicit content template wrapping ng-content. */
     readonly implicitContentTemplate: _angular_core.Signal<TemplateRef<unknown> | undefined>;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<TabComponent, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<TabComponent, "tw-tab", never, { "value": { "alias": "value"; "required": true; "isSignal": true; }; "label": { "alias": "label"; "required": false; "isSignal": true; }; "disabled": { "alias": "disabled"; "required": false; "isSignal": true; }; "closable": { "alias": "closable"; "required": false; "isSignal": true; }; "lazy": { "alias": "lazy"; "required": false; "isSignal": true; }; }, {}, ["triggerTemplate", "contentTemplate"], ["*"], true, never>;
+    static ɵcmp: _angular_core.ɵɵComponentDeclaration<TabComponent, "tw-tab", never, { "value": { "alias": "value"; "required": true; "isSignal": true; }; "label": { "alias": "label"; "required": false; "isSignal": true; }; "disabled": { "alias": "disabled"; "required": false; "isSignal": true; }; "closable": { "alias": "closable"; "required": false; "isSignal": true; }; "dismissible": { "alias": "dismissible"; "required": false; "isSignal": true; }; "lazy": { "alias": "lazy"; "required": false; "isSignal": true; }; }, {}, ["triggerTemplate", "contentTemplate"], ["*"], true, never>;
 }
 declare class TabTriggerElementDirective implements FocusableOption {
     readonly elementRef: ElementRef<any>;

package/types/cdevhub-ngx-tw-theme.d.ts

@@ -41,7 +41,24 @@ interface TwThemeConfig {
      * the service never does.
      */
     storageKey?: string;
-    /** The HTML attribute written to the target element. Defaults to `'data-theme'`. */
+    /**
+     * The HTML attribute written to the target element. Defaults to `'data-theme'`.
+     *
+     * @deprecated Changing this breaks theming, and cannot be made to work. The
+     * shipped stylesheets key off the **literal** `data-theme` — `_light.css`,
+     * `_dark.css` and both high-contrast files each declare an element-agnostic
+     * `[data-theme="…"]` block, and CSS cannot parameterise an attribute name. So
+     * a renamed attribute matches none of them: `ThemeService.applyToElement()`
+     * writes the new name and nothing reacts, while `ThemeDirective` ignores this
+     * option entirely and keeps writing `data-theme` (which is the only reason
+     * `[twTheme]` still works when it is set). Two of the three consumers
+     * therefore disagree with it by design.
+     *
+     * It is deprecated rather than removed because removing it is a breaking
+     * change; it will go in the next major. To scope a theme to a subtree use the
+     * `[twTheme]` directive, and to retheme, override the semantic tokens in your
+     * own `@theme` block rather than renaming the attribute they hang off.
+     */
     attribute?: string;
     /** Which element receives the theme attribute. Defaults to `'documentElement'`. */
     target?: 'documentElement' | 'body';