@zambon-dev/library 1.3.1 → 1.3.2

package/CHANGELOG.md

@@ -23,7 +23,72 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### ⚠ Breaking Changes / Migration
 
-## [1.3.0] - 2026-07-28
+## [1.3.2] - 2026-07-30
+
+### Added
+
+- **Storybook: `Data Grid/Data Grid ▸ Multi Select Tall Rows` story** — multi-selection over rows
+  taller than the default `rowHeight` (41.6px), the height a row needs once it shows a thumbnail.
+  Misalignment in the selection column is obvious at that height, so this is the story to check the
+  selection checkbox against. Development-only: stories are excluded from the package build.
+
+### Changed
+
+- **`lib-ribbon` now hides itself when it contains no visible buttons.** A screen with no ribbon
+  actions — a dashboard, or any view that projects an empty `#ribbon` template — previously still
+  rendered the bar's border, background and padding around nothing, wasting vertical space at the top
+  of the page. This mirrors `lib-ribbon-group`, which already hid itself when none of its children
+  were visible. Ribbons with at least one visible group are unaffected. See
+  **⚠ Breaking Changes / Migration** below.
+
+### Fixed
+
+- **`lib-data-grid`'s multi-selection checkbox is now vertically centred in the row.** The checkbox is
+  styled with `vertical-align: super`, which lifts it off the middle of its line box — roughly 6px at
+  the default font size. At the default `configs.rowHeight` (41.6px) the drift is easy to miss, but on
+  taller rows (say `rowHeight: 56` for a row showing a thumbnail) the checkbox visibly hugged the top
+  of the row while the text columns stayed centred. The selection cell now lays its checkbox out as a
+  flex item, so it is centred by the box model and `vertical-align` no longer applies to it. The cell
+  is also tagged with a `selection` class, mirroring the header's `header-cell selection`. Horizontal
+  placement is unchanged, and no consumer changes are required.
+- **Form inputs no longer render a stray bordered box when `type` is set as a static attribute.**
+  Angular keeps static attributes in the DOM even when a directive consumes them as an `@Input()`, so
+  `<lib-form-input-group type="checkbox">` left a `type="checkbox"` attribute on the host element —
+  where `@tailwindcss/forms`' tag-agnostic `[type="checkbox"]` base rules styled the host itself as a
+  checkbox (1px border, white fill, `height: 1rem`), drawing an empty-input box around the field row
+  and tinting its icon. `FormInputGroupComponent` and `FormInputComponent` now clear the attribute via
+  a host binding. This affects every value of `type` (`checkbox`, `date`, `number`, `password`, …);
+  both `type="checkbox"` and `[type]="'checkbox'"` now render identically, so existing call sites are
+  fixed with no changes required.
+- **`lib-multi-editor` no longer discards rows the user did not type into.** `MultiEditorDataset.newData()`
+  exists so implementations can pre-fill a new row, but `onNewClick` reached the form through
+  `reset()` + `patchValue()`, which leaves it pristine — and the change tracker only records a row
+  while `formGroup.dirty`. Pre-filled values were therefore shown in the grid and then dropped from
+  the save batch. The visible symptom was worse than lost defaults: adding several rows and editing
+  only the last one saved just that row, because `onSaveClick` validates the current selection only,
+  so the earlier rows silently vanished on refresh. `newData()`'s values are now registered when the
+  row is added.
+
+### ⚠ Breaking Changes / Migration
+
+`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
+dropped, so a batch may contain entries it did not before; verify your backend rejects or defaults
+them as you expect.
+
+`lib-ribbon` now hides itself when it has neither a visible `lib-ribbon-group` nor any other
+projected content. No action needed if your ribbons use groups (the normal case). The rule is a
+global selector at specificity (0,1,2), so overriding it requires `!important`. Because the bar can
+now appear and disappear rather than merely resize, anything positioned relative to the ribbon may
+shift when a button's visibility resolves (e.g. as permissions arrive).
+
+## [1.3.1] - 2026-07-28
+
+> There is no `1.3.0` on npm: the version number was taken by an early publish that was later
+> unpublished, and npm never allows a retired version number to be reused. The sidebar rework below
+> therefore shipped as `1.3.1`. Upgrade straight from `1.2.0` to `1.3.1`.
 
 ### Added
 
@@ -90,7 +155,8 @@ 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.3.0...HEAD
-[1.3.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.3.0
+[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/library-v1.3.2...HEAD
+[1.3.2]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.3.2
+[1.3.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.3.1
 [1.2.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.2.0
 [1.1.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/library-v1.1.1