@ethlete/cdk 5.0.0-next.23 → 5.0.0-next.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,22 @@
1
1
  # @ethlete/cdk
2
2
 
3
+ ## 5.0.0-next.24
4
+
5
+ ### Patch Changes
6
+
7
+ - [#3041](https://github.com/ethlete-io/ethdk/pull/3041) [`6c9d38d`](https://github.com/ethlete-io/ethdk/commit/6c9d38d7e6b41586d7c9abb3296e5f45ccc3767c) Thanks [@github-actions](https://github.com/apps/github-actions)! - `@ethlete/core` no longer depends on `@angular/cdk`: `injectBreakpointObserver()` is a plain
8
+ `matchMedia` implementation (same API), and `AnimatedOverlayDirective` moved to `@ethlete/cdk` -
9
+ import it from there.
10
+
11
+ - [#3041](https://github.com/ethlete-io/ethdk/pull/3041) [`353777b`](https://github.com/ethlete-io/ethdk/commit/353777bb56e42ad1c02058a2ccf694f69c94b025) Thanks [@github-actions](https://github.com/apps/github-actions)! - Mark build-tooling peer dependencies (`vite`, `typescript`, `ts-morph`, `@nx/devkit`, `@analogjs/*`) and feature-scoped runtime peers (`date-fns` in components) as optional via `peerDependenciesMeta`. They are only needed when running the Nx generators or using the date/time components - consumers no longer have to install them just to use the libraries.
12
+
13
+ - [#3041](https://github.com/ethlete-io/ethdk/pull/3041) [`42ec970`](https://github.com/ethlete-io/ethdk/commit/42ec970d6963bb5a3aa3af4e207ef2cac801c915) Thanks [@github-actions](https://github.com/apps/github-actions)! - DI: `createProvider` / `createRootProvider` / `createStaticProvider` / `createStaticRootProvider` /
14
+ `createLabels` are replaced by `defineProvider` & co., which return a definition you read with
15
+ `toProvideFn` / `toInjectFn` / `toToken`; `createQueryClient`, `createBearerAuthProvider` and
16
+ `createWebSocketClient` return that definition instead of a tuple. Every `provideX` / `injectX` /
17
+ token export keeps its name - run `nx g @ethlete/core:migrate-provider-shape` for your own call sites.
18
+ Cuts the `@ethlete/components` import floor from 89.9 to 2.4 kB gz.
19
+
3
20
  ## 5.0.0-next.23
4
21
 
5
22
  ### Patch Changes
@@ -8,11 +25,11 @@
8
25
 
9
26
  - [#3037](https://github.com/ethlete-io/ethdk/pull/3037) [`3151b7a`](https://github.com/ethlete-io/ethdk/commit/3151b7a253d14e38e22e20d67bf0191f141c144e) Thanks [@github-actions](https://github.com/apps/github-actions)! - Add `ethlete/no-template-literal-before-inline-template`, and restructure the files it flagged.
10
27
 
11
- The Angular VS Code extension decides **client-side** whether the cursor sits inside an inline `template:` before it forwards completion, hover, go-to-definition or signature-help to the language server. That check (`isNotTypescriptOrSupportedDecoratorField`) walks the file with a bare `ts.createScanner()` loop, which cannot re-scan `}` as `TemplateMiddle`/`TemplateTail` — that needs the parser's `reScanTemplateToken()`. So the first template literal containing a `${…}` substitution desynchronises both the token stream and the brace counter, the scanner never recognises `template` `:` again, and every template request below it is dropped. The language server answers those requests correctly; the editor just never asks, so the template silently has no IntelliSense at all.
28
+ The Angular VS Code extension decides **client-side** whether the cursor sits inside an inline `template:` before it forwards completion, hover, go-to-definition or signature-help to the language server. That check (`isNotTypescriptOrSupportedDecoratorField`) walks the file with a bare `ts.createScanner()` loop, which cannot re-scan `}` as `TemplateMiddle`/`TemplateTail` - that needs the parser's `reScanTemplateToken()`. So the first template literal containing a `${…}` substitution desynchronises both the token stream and the brace counter, the scanner never recognises `template` `:` again, and every template request below it is dropped. The language server answers those requests correctly; the editor just never asks, so the template silently has no IntelliSense at all.
12
29
 
13
- The new rule reproduces that scanner verbatim, so it reports exactly the templates the extension would abandon — no heuristic. Twenty inline templates across `components`, `cdk` and the playground were affected, all of them behind a fixture or helper that happened to use an interpolated template literal. Story fixtures moved into sibling `*-storybook.data.ts` files; spec fixtures and in-class helpers that must stay above their component (because a later `@Component` references the class in `imports`) were rewritten without the interpolation.
30
+ The new rule reproduces that scanner verbatim, so it reports exactly the templates the extension would abandon - no heuristic. Twenty inline templates across `components`, `cdk` and the playground were affected, all of them behind a fixture or helper that happened to use an interpolated template literal. Story fixtures moved into sibling `*-storybook.data.ts` files; spec fixtures and in-class helpers that must stay above their component (because a later `@Component` references the class in `imports`) were rewritten without the interpolation.
14
31
 
15
- No public API changed — the `components` and `cdk` bumps are story/spec restructuring plus moving `signalVisibilityChangeClasses` below `RichFilterHostComponent` in the same module.
32
+ No public API changed - the `components` and `cdk` bumps are story/spec restructuring plus moving `signalVisibilityChangeClasses` below `RichFilterHostComponent` in the same module.
16
33
 
17
34
  ## 5.0.0-next.22
18
35
 
@@ -29,7 +46,7 @@
29
46
  `et-menu`, `et-radio`, `et-select`, `et-checkbox`, `et-tooltip`, …), apps that
30
47
  consume both libraries at once can no longer target one without hitting the
31
48
  other. Every cdk element now carries `et-legacy` alongside its usual classes, so
32
- consumer overrides can be scoped to the cdk implementation only — e.g. rewrite
49
+ consumer overrides can be scoped to the cdk implementation only - e.g. rewrite
33
50
  `.et-overlay { … }` as `.et-overlay.et-legacy { … }`. The marker is inert (no cdk
34
51
  CSS references it), so cdk rendering is unchanged.
35
52
 
@@ -82,11 +99,11 @@
82
99
 
83
100
  - [#2996](https://github.com/ethlete-io/ethdk/pull/2996) [`b64e055`](https://github.com/ethlete-io/ethdk/commit/b64e0553c6480d5efde342675fd09899f0d45c0f) Thanks [@baltruschat](https://github.com/baltruschat)! - Position winner rounds correctly when the winner bracket starts after round 1
84
101
 
85
- Some double elimination brackets omit the early winner rounds — e.g. a small bracket where the first lower round is seeded directly from a group phase and has no winner round feeding it. The grid previously placed the first present winner round in the leftmost column, so every winner round was one column too far left relative to its drop-in lower round. The grid now detects the missing leading winner rounds (a complete winner bracket has lowerRounds / 2 + 1 rounds) and leaves those leading slots empty, so each present winner round lines up above the lower round its losers actually drop into.
102
+ Some double elimination brackets omit the early winner rounds - e.g. a small bracket where the first lower round is seeded directly from a group phase and has no winner round feeding it. The grid previously placed the first present winner round in the leftmost column, so every winner round was one column too far left relative to its drop-in lower round. The grid now detects the missing leading winner rounds (a complete winner bracket has lowerRounds / 2 + 1 rounds) and leaves those leading slots empty, so each present winner round lines up above the lower round its losers actually drop into.
86
103
 
87
104
  - [#2996](https://github.com/ethlete-io/ethdk/pull/2996) [`b64e055`](https://github.com/ethlete-io/ethdk/commit/b64e0553c6480d5efde342675fd09899f0d45c0f) Thanks [@baltruschat](https://github.com/baltruschat)! - Align winner bracket rounds above their drop-in loser round
88
105
 
89
- In the double elimination grid, winner bracket rounds that span two lower bracket columns were centered over that span, leaving them half a column off from the loser round they relate to. They are now left-aligned within the span so winner round n sits directly above the loser round its losers drop into (round 2n − 2) — the round whose matches merge into the next one — making the drop target unambiguous. The first winner round and the winner final are single-column and stay in place; lower rounds and other brackets are unaffected.
106
+ In the double elimination grid, winner bracket rounds that span two lower bracket columns were centered over that span, leaving them half a column off from the loser round they relate to. They are now left-aligned within the span so winner round n sits directly above the loser round its losers drop into (round 2n − 2) - the round whose matches merge into the next one - making the drop target unambiguous. The first winner round and the winner final are single-column and stay in place; lower rounds and other brackets are unaffected.
90
107
 
91
108
  - [#2996](https://github.com/ethlete-io/ethdk/pull/2996) [`b64e055`](https://github.com/ethlete-io/ethdk/commit/b64e0553c6480d5efde342675fd09899f0d45c0f) Thanks [@baltruschat](https://github.com/baltruschat)! - Fix rendering of truncated double elimination brackets
92
109