@zambon-dev/shared 3.0.0 → 3.0.1

package/CHANGELOG.md

@@ -23,6 +23,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### ⚠ Breaking Changes / Migration
 
+## [3.0.1] - 2026-09-21
+
+### Changed
+
+- `LoginLayoutComponent`, `HomeComponent`, `BrandComponent` and `EnvironmentBadgeComponent` now
+  use `ChangeDetectionStrategy.OnPush`. Behaviour is unchanged; they render from inputs or from
+  immutable application config.
+
+- **Accessibility.** The operations-history row opens its detail modal from the keyboard as well as
+  the mouse.
+
 ## [3.0.0] - 2026-09-21
 
 ### Changed
@@ -46,6 +57,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 **Requires `@zambon-dev/library` 2.x and `@zambon-dev/framework` 2.x.** Both peer ranges moved to
 `^2.0.0`. See the library changelog for the `FormInputComponent` output renames.
+
 ## [2.1.1] - 2026-09-15
 
 ### Fixed
@@ -61,8 +73,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   is decidable up front, so `ExternalContentComponent` now compares the page’s protocol with the
   destination’s and shows a message naming the real reason. **Open in a new browser tab keeps
   working and is the way out:** a top-level navigation to `http://` is not mixed content. For a
-  destination that only speaks `http`, configure the menu item as *external, new tab* rather than
-  *external, embedded*; to embed it, put it behind an `https` reverse proxy.
+  destination that only speaks `http`, configure the menu item as _external, new tab_ rather than
+  _external, embedded_; to embed it, put it behind an `https` reverse proxy.
 
   Two new keys, `ExternalContent-Insecure-Title` and `ExternalContent-Insecure-Message`, ship in
   `en` and `pt`. An application that overrides this feature’s translations needs to add them.
@@ -127,7 +139,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
   The tab URL is `/external-content/<menu id>` and never carries the destination, so no one can
   hand-craft a link that makes your application frame an arbitrary site. Pressing F5 on an embedded
-  tab restores both the frame and the tab title from `sessionStorage`. Opening that URL in a *fresh*
+  tab restores both the frame and the tab title from `sessionStorage`. Opening that URL in a _fresh_
   browser tab can only work if your `SidebarService.getMenuFromUrl()` resolves
   `/external-content/<id>`; otherwise the view says the content is unavailable and asks the user to
   reopen it from the menu.
@@ -186,6 +198,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   detail-views through the real hosts (`DefaultTabViewComponent` /
   `DefaultDetailsTabViewComponent`, `TabViewList` / `FormView`, and the `framework-button-*`
   ribbon buttons). It covers:
+
   - a branded top bar (logo, app name, subtitle, environment badge and a working notifications
     bell) and a versioned sidebar footer;
   - a mocked audit/history view, reachable from the detail views' Views button;
@@ -210,7 +223,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `IServicesHistoryList` and `IOperationsHistoryList` declared an `ID` property, and
   `IOperationsHistoryList` declared `entityId`. Neither key is ever sent. The audit endpoints
   (`POST /{controller}/{entityID}/Audit` and `.../Audit/{serviceHistoryID}`) serialize under
-  ASP.NET Core's default camelCase policy, which lowercases only a *leading* run of capitals — so the
+  ASP.NET Core's default camelCase policy, which lowercases only a _leading_ run of capitals — so the
   backend's `ID` goes out as `id` and its `EntityID` goes out as `entityID`. Typing a row against
   `.ID` or `.entityId` therefore compiled fine and read `undefined` at run time. See
   **⚠ Breaking Changes / Migration** below.
@@ -239,10 +252,10 @@ Two properties on the audit history models were renamed to the keys the backend
 models are exported from the package root, so anything typed against the old names will now fail to
 compile. Nothing in `@shared` changes behaviour at run time — the fix is to the declared types.
 
-| Model | Before | After |
-|-------|--------|-------|
-| `IServicesHistoryList` | `ID: number` | `id: number` |
-| `IOperationsHistoryList` | `ID: number` | `id: number` |
+| Model                    | Before              | After               |
+| ------------------------ | ------------------- | ------------------- |
+| `IServicesHistoryList`   | `ID: number`        | `id: number`        |
+| `IOperationsHistoryList` | `ID: number`        | `id: number`        |
 | `IOperationsHistoryList` | `entityId?: number` | `entityID?: number` |
 
 To upgrade:
@@ -344,7 +357,8 @@ URL) in `AppConfig`, and implement a hub that pushes the notification list to cl
   available via [GitHub Releases](https://github.com/RicardoZambon/ZLibraries/releases) and the
   `shared-v*` tags.
 
-[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/shared-v3.0.0...HEAD
+[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/shared-v3.0.1...HEAD
+[3.0.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/shared-v3.0.1
 [3.0.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/shared-v3.0.0
 [2.1.3]: https://github.com/RicardoZambon/ZLibraries/releases/tag/shared-v2.1.3
 [2.1.2]: https://github.com/RicardoZambon/ZLibraries/releases/tag/shared-v2.1.2

package/README.md

@@ -17,20 +17,20 @@ npm install @zambon-dev/shared
 
 All peers must be present in the consuming application:
 
-| Package | Range |
-| --- | --- |
-| `@angular/common` | `^19.1.0` |
-| `@angular/core` | `^19.1.0` |
-| `@angular/forms` | `^19.1.0` |
-| `@angular/platform-browser` | `^19.1.0` |
-| `@angular/router` | `^19.1.0` |
-| `@auth0/angular-jwt` | `^5.2.0` |
-| `@microsoft/signalr` | `^10.0.0` |
-| `@ngx-translate/core` | `^16.0.4` |
-| `@zambon-dev/framework` | `^1.0.0` |
-| `@zambon-dev/library` | `^1.0.0` |
+| Package                           | Range     |
+| --------------------------------- | --------- |
+| `@angular/common`                 | `^19.1.0` |
+| `@angular/core`                   | `^19.1.0` |
+| `@angular/forms`                  | `^19.1.0` |
+| `@angular/platform-browser`       | `^19.1.0` |
+| `@angular/router`                 | `^19.1.0` |
+| `@auth0/angular-jwt`              | `^5.2.0`  |
+| `@microsoft/signalr`              | `^10.0.0` |
+| `@ngx-translate/core`             | `^16.0.4` |
+| `@zambon-dev/framework`           | `^1.0.0`  |
+| `@zambon-dev/library`             | `^1.0.0`  |
 | `ngx-translate-multi-http-loader` | `^19.0.2` |
-| `rxjs` | `^7.8.0` |
+| `rxjs`                            | `^7.8.0`  |
 
 ## Usage
 
@@ -51,9 +51,7 @@ Route protection uses the exported guard:
 ```ts
 import { AuthGuard } from '@zambon-dev/shared';
 
-export const routes: Routes = [
-  { path: 'orders', component: OrdersComponent, canActivate: [AuthGuard] },
-];
+export const routes: Routes = [{ path: 'orders', component: OrdersComponent, canActivate: [AuthGuard] }];
 ```
 
 Unauthenticated visitors are redirected to `/login` with a `returnUrl` query parameter.