@zambon-dev/library 1.6.4 → 2.0.1

package/CHANGELOG.md

@@ -23,6 +23,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### ⚠ Breaking Changes / Migration
 
+## [2.0.1] - 2026-09-21
+
+### Changed
+
+- `RibbonComponent`, `FormGroupComponent` and `GroupContainerComponent` now use
+  `ChangeDetectionStrategy.OnPush`. They render from their inputs only, so behaviour is
+  unchanged, but consuming applications no longer check them on every change detection pass.
+
+## [2.0.0] - 2026-09-21
+
+### Changed
+
+- **Accessibility.** Every interactive element that previously responded only to a mouse is now
+  reachable and operable by keyboard. `RibbonButtonComponent` (button, dropdown toggle and each
+  option), `GroupAccordionComponent`, `GroupScrollSpyComponent`, `SidebarItemComponent` and the
+  `MultiSelectComponent` result grid gained focus, `Enter`/`Space` activation and the matching ARIA
+  roles and state. `CatalogSelectComponent` status rows are now `role="presentation"`; its retry
+  action is a real button.
+- `MultiEditorComponent` and the multi-select result grid render their actions as `<button>`
+  rather than `<a>`. They are styled identically but now honour `disabled` natively.
+
 ## [1.6.4] - 2026-09-21
 
 ### Fixed
@@ -39,6 +60,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `@zambon-dev/library` on its own left the dependency unresolved.
 - Added a README to the published package.
 
+### ⚠ Breaking Changes / Migration
+
+**`FormInputComponent` outputs renamed.** Four outputs were named after native DOM events. Because
+`<lib-form-input>` is a real element, `(change)` and `(input)` fired a consumer's handler twice --
+once from the native event bubbling out of the inner control, once from the component -- and
+`(blur)`/`(focus)` shadowed the native events. All four are typed `any`, so TypeScript could not
+catch the mismatch.
+
+Rename the bindings in your templates:
+
+| Before     | After            |
+| ---------- | ---------------- |
+| `(blur)`   | `(blurred)`      |
+| `(change)` | `(changed)`      |
+| `(focus)`  | `(focused)`      |
+| `(input)`  | `(inputChanged)` |
+
+`(fixedValueChanged)` is unchanged, but its payload type is now `string` instead of `any` --
+matching what it always emitted.
+
+If you were relying on the double-fire, expect one call per event now instead of two.
+
 ## [1.6.2] - 2026-09-20
 
 ### Fixed
@@ -120,7 +163,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   The point is where the grouping lives. `region` is a label repeated on every item that belongs to
   a group, matched by exact string equality: a typo silently splits one area into two, and the
   area has no row of its own to carry an order or a translation. Derived from the tree, the area
-  *is* a menu row — it already has a translated label and an order — and nothing has to be
+  _is_ a menu row — it already has a translated label and an order — and nothing has to be
   duplicated across its items.
 
   The children of an area are fetched **eagerly**, at load, because they are rendered without a
@@ -250,7 +293,7 @@ and want external items too, add a subscription to `menuExternalUrlSelected`.
 `lib-multi-editor` now sends rows that `newData()` pre-filled but the user never edited. Nothing to do
 if your `newData()` returns an empty object (`{}`) — the common "blank row" convention — since a
 value-less row is still skipped and the posted batch is byte-for-byte what it was before. If your
-`newData()` *does* return field values, those rows now reach `saveData()` where they were previously
+`newData()` _does_ return field values, those rows now reach `saveData()` where they were previously
 dropped, so a batch may contain entries it did not before; verify your backend rejects or defaults
 them as you expect.
 
@@ -331,7 +374,9 @@ config options and the `getUserProfile()` method still exist but are no longer c
   available via [GitHub Releases](https://github.com/RicardoZambon/ZLibraries/releases) and the
   `library-v*` tags.
 
-[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/library-v1.6.4...HEAD
+[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/library-v2.0.1...HEAD
+[2.0.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v2.0.1
+[2.0.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v2.0.0
 [1.6.4]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.6.4
 [1.6.3]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.6.3
 [1.6.2]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.6.2

package/README.md

@@ -17,16 +17,16 @@ npm install @zambon-dev/library
 
 All peers must be present in the consuming application:
 
-| Package | Range |
-| --- | --- |
-| `@angular/cdk` | `^19.1.5` |
-| `@angular/common` | `^19.1.0` |
-| `@angular/core` | `^19.1.0` |
-| `@angular/forms` | `^19.1.0` |
-| `@angular/router` | `^19.1.0` |
+| Package               | Range     |
+| --------------------- | --------- |
+| `@angular/cdk`        | `^19.1.5` |
+| `@angular/common`     | `^19.1.0` |
+| `@angular/core`       | `^19.1.0` |
+| `@angular/forms`      | `^19.1.0` |
+| `@angular/router`     | `^19.1.0` |
 | `@ngx-translate/core` | `^16.0.4` |
-| `ngx-resize-observer` | `^3.0.0` |
-| `rxjs` | `^7.8.0` |
+| `ngx-resize-observer` | `^3.0.0`  |
+| `rxjs`                | `^7.8.0`  |
 
 ## Usage
 
@@ -74,7 +74,9 @@ Helpers, models, configuration providers, services and validators are exported f
 
 ## Documentation
 
-Component behaviour and variants are documented as Storybook stories alongside the source. To browse them:
+Browse the published Storybook at [https://ricardozambon.github.io/ZLibraries/library/](https://ricardozambon.github.io/ZLibraries/library/).
+
+Component behaviour and variants are documented as stories alongside the source. To run it locally:
 
 ```bash
 npm run storybook:library