ngwr 14.4.0 → 14.5.1

package/schematics/migrations/v14/index.js

@@ -101,28 +101,57 @@ Object.defineProperty(exports, "__esModule", { value: true });
  * Both are now zero for an app that does not opt in.
  */
 const IGNORE_DIRS = new Set(['node_modules', 'dist', '.git', '.cache', '.angular', 'coverage', '.next', '.nuxt']);
+/**
+ * What an open tag may hold between its name and the attribute a rule is after:
+ * a quoted value, consumed only as a PAIR, or any one character that is neither
+ * a quote nor `>`. Every element-scoped rule and attribute detector in this file
+ * is built on it, and both halves of "only as a pair" were earned.
+ *
+ * Stepping OVER a quoted value is what a plain `[^>]*?` got wrong: a `>` inside a
+ * binding looks like the end of the tag, so
+ * `<wr-alert [type]="n > 0 ? 'a' : 'b'" closeable>` left `closeable` behind while
+ * the same attributes in the other order moved. The leftover is SILENT — a static
+ * `closeable` / `totalItems="42"` that matches no input is an ordinary DOM
+ * attribute and `strictTemplates` says nothing, so the alert quietly loses its
+ * dismiss button. (Bracketed forms are loud: NG8002.)
+ *
+ * Never consuming a LONE quote is what the first fix got wrong. It spelled the
+ * fallback `[^>]`, which matches a quote as well, so the engine could backtrack
+ * into a single-quoted span that STARTS at the apostrophe inside `title="it's"`
+ * and runs past `/>` into the following element: `<wr-alert title="it's" />`
+ * then `<app-panel [label]="'x'" closeable />` renamed the PANEL's attribute. The
+ * same overlap made a miss exponential — one `<wr-alert>` holding twenty-two
+ * quoted attributes and nothing to rename took sixteen seconds in the bare
+ * `closeable` rule alone, where this form takes under a millisecond. And a miss
+ * did not stay inside its tag: since a pair may contain `>`, a pairing that
+ * started at a CLOSING quote jumped over `/>` into later elements, so an
+ * ordinary element without the attribute sent the search across the rest of the
+ * file. On a 64-line template that never finished, and because `ng update`
+ * commits each migration's tree separately, v12 and v13 landed while this one
+ * wrote nothing. The spec's timing cases are sized to fail in seconds on that form.
+ *
+ * What it guarantees: a match cannot leave the open tag it started in, as long as
+ * every quote in that tag opens or closes an attribute value. The one markup that
+ * breaks the condition is an UNQUOTED value holding a quote (`title=it's`), and a
+ * tag like that is skipped rather than guessed at — which costs nothing real,
+ * because Angular's own template parser refuses it (`Opening tag "input" not
+ * terminated.`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 /**
  * An open tag, up to and including the whitespace before some attribute.
- * `[^>]*?` cannot cross a `>`, so a rename can never escape the element it is
- * scoped to, however the tag wraps across lines.
  *
  * The anchor is `(?![-\w])` and NOT `\b`: a word boundary still matches at the
  * front of a longer element name, which is how a v9-shaped rule would have
  * renamed an attribute on `<wr-table-filter>` while claiming to touch only
  * `<wr-table>`. Every one of these four has such a neighbour — `wr-table-filter`
  * and `wr-table-sort`, `wr-window-container` and `wr-window-taskbar` — or would
- * acquire one the moment the catalog grows.
- *
- * Quoted values are stepped over rather than excluded, and that is the half a
- * plain `[^>]*?` gets wrong: a `>` inside a binding expression looks like the end
- * of the tag, so `<wr-alert [type]="n > 0 ? 'a' : 'b'" closeable>` left
- * `closeable` behind while the same attributes in the other order moved. The
- * leftover is SILENT — a static `closeable` / `totalItems="42"` that matches no
- * input is an ordinary DOM attribute and `strictTemplates` says nothing, so the
- * alert quietly loses its dismiss button. (Bracketed forms are loud: NG8002.)
- * `migration-v9` carries the same anchoring and the same hole.
+ * acquire one the moment the catalog grows. `migration-v9` carries the same
+ * anchoring and the same pattern.
  */
-const openTag = (name) => String.raw `<${name}(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s`;
+const openTag = (name) => String.raw `<${name}(?![-\w])${IN_TAG}\s`;
+/** The two elements `[wrInput]` applies to — its selector is `input[wrInput], textarea[wrInput]`. */
+const FIELD = String.raw `<(?:input|textarea)(?![-\w])`;
 const ALERT = openTag('wr-alert');
 const TABLE = openTag('wr-table');
 const PAGER = openTag('wr-pagination');
@@ -143,21 +172,15 @@ const HTML_TRANSFORMS = [
     // native attribute, so rewriting one that was never ngwr's silently rebinds a
     // character-width hint. The two orders are both real markup, hence two rules.
     {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\swrInput(?:"[^"]*"|'[^']*'|[^>])*?\s)\[wrSize\]/g,
+        pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\swrInput${IN_TAG}\s)\[wrSize\]`, 'g'),
         replacement: '$1[size]',
     },
+    { pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\swrInput${IN_TAG}\s)wrSize=`, 'g'), replacement: '$1size=' },
     {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\swrInput(?:"[^"]*"|'[^']*'|[^>])*?\s)wrSize=/g,
-        replacement: '$1size=',
-    },
-    {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s)\[wrSize\]((?:"[^"]*"|'[^']*'|[^>])*?\swrInput)/g,
+        pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\s)\[wrSize\](${IN_TAG}\swrInput)`, 'g'),
         replacement: '$1[size]$2',
     },
-    {
-        pattern: /(<(?:input|textarea)(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s)wrSize=((?:"[^"]*"|'[^']*'|[^>])*?\swrInput)/g,
-        replacement: '$1size=$2',
-    },
+    { pattern: new RegExp(String.raw `(${FIELD}${IN_TAG}\s)wrSize=(${IN_TAG}\swrInput)`, 'g'), replacement: '$1size=$2' },
     // <wr-table>, from [totalItems] to [total]
     { pattern: new RegExp(`(${TABLE})\\[totalItems\\]`, 'g'), replacement: '$1[total]' },
     { pattern: new RegExp(`(${TABLE})totalItems=`, 'g'), replacement: '$1total=' },
@@ -202,8 +225,12 @@ const GLOBAL_TRANSFORMS = [
     // keyed on it stops matching with no error — CSS does not have one.
     { pattern: /\bwr-window--chrome-normal\b/g, replacement: 'wr-window--chrome-md' },
 ];
-/** `<wr-tab …>` carrying a `routerLink`, however the tag is wrapped across lines. */
-const ROUTER_TAB = /<wr-tab\b[^>]*\brouterLink\b/;
+/**
+ * `<wr-tab …>` carrying a `routerLink`, however the tag is wrapped across lines
+ * and whatever an earlier binding compares — the plain `[^>]*` this used to be
+ * read `[disabled]="n > 0"` as the end of the tag and reported nothing.
+ */
+const ROUTER_TAB = new RegExp(String.raw `<wr-tab(?![-\w])${IN_TAG}\brouterLink\b`);
 const LOADING_BAR = /<wr-loading-bar\b/;
 /** `provideWrDateAdapter(` with no `locale:` before the call closes. */
 // `locale` as a key OR as shorthand, and the scan for it runs to the call's own
@@ -217,8 +244,20 @@ const DATE_ADAPTER_NO_LOCALE = /\bprovideWrDateAdapter\(\s*(?:\)|\{(?![\s\S]*?\b
 /** `provideWrI18n(` with no `defaultLocale:` before the call closes. */
 const I18N_NO_DEFAULT_LOCALE = /\bprovideWrI18n\(\s*(?:\)|\{(?![^})]*\bdefaultLocale\s*:))/;
 const DEFAULT_CONFIG = /\bDEFAULT_WR_I18N_CONFIG\b/;
-/** `ofLabel` on a pagination tag, bound (`[ofLabel]`) or static. */
-const OF_LABEL = /<wr-pagination\b[^>]*\[?ofLabel\]?\s*=/;
+/** `ofLabel` on a pagination tag, bound (`[ofLabel]`) or static, wherever it sits in the tag. */
+const OF_LABEL = new RegExp(String.raw `${PAGER}\[?ofLabel\]?\s*=`);
+/**
+ * `wrSize` still on a `[wrInput]` field AFTER the renames ran, in either
+ * attribute order and with any spacing around `=`. The renames read `wrSize=` and
+ * `[wrSize]` exactly, and whatever they do not move is silent: a static `wrSize`
+ * matches no input, lands on the field as a plain DOM attribute, and the control
+ * renders at its default size. So this is the one detector that reads the
+ * REWRITTEN text — its whole job is what the rules left behind.
+ */
+const LEFTOVER_WR_SIZE = [
+    new RegExp(String.raw `${FIELD}${IN_TAG}\swrInput${IN_TAG}\s\[?wrSize\]?\s*=`),
+    new RegExp(String.raw `${FIELD}${IN_TAG}\s\[?wrSize\]?\s*=${IN_TAG}\swrInput`),
+];
 // The half `OF_LABEL` cannot see. Apps that never bound the input still
 // translated the key, and `pagination.of` is gone: the range is one
 // `pagination.range` template now, so a catalog that defines the old key loses
@@ -285,6 +324,7 @@ function ngUpdateV14() {
         const defaultConfigs = [];
         const ofLabels = [];
         const staleCatalogs = [];
+        const leftoverSizes = [];
         let rewritten = 0;
         visit(tree, '/', filePath => {
             const lower = filePath.toLowerCase();
@@ -295,10 +335,11 @@ function ngUpdateV14() {
             // reach stylesheets too, because one of them is a BEM class.
             if (!isTs && !isHtml && !isStyle && !lower.endsWith('.json'))
                 return;
-            // Read ONCE. Every detector below then answers about the file the user
-            // wrote, not about the file a transform left behind — none of the five
-            // renames touches a reported token today, and relying on that is exactly
-            // the coupling that breaks the next time one is added.
+            // Read ONCE. Every detector below but the leftover `wrSize` check then
+            // answers about the file the user wrote, not about the file a transform
+            // left behind — none of the six renames touches a token those detectors
+            // report today, and relying on that is exactly the coupling that breaks
+            // the next time one is added.
             const content = tree.readText(filePath);
             if (isTs || isHtml || isStyle) {
                 const next = apply(content, [
@@ -310,6 +351,11 @@ function ngUpdateV14() {
                     tree.overwrite(filePath, next);
                     rewritten += 1;
                 }
+                // The one detector that reads what the renames LEFT rather than what the
+                // user wrote: a `wrSize` surviving them is exactly what it exists to name.
+                if ((isTs || isHtml) && LEFTOVER_WR_SIZE.some(pattern => pattern.test(next))) {
+                    leftoverSizes.push(filePath);
+                }
             }
             if (ROUTER_TAB.test(content))
                 routerTabs.push(filePath);
@@ -333,10 +379,19 @@ function ngUpdateV14() {
             context.logger.info(`ngwr v14 migration: rewrote ${rewritten} file(s) for the renames: on <wr-alert> from ` +
                 'closeable to closable, on <wr-table> from totalItems to total, on <wr-pagination> from ' +
                 'currentPage to page (and from currentPageChange to pageChange), from isDisabledWhenLoading ' +
-                'to disabledWhenLoading, and the window chromeSize scale from compact/normal to sm/md ' +
-                '(class .wr-window--chrome-compact to --chrome-sm).');
+                'to disabledWhenLoading, the window chromeSize scale from compact/normal to sm/md ' +
+                '(class .wr-window--chrome-compact to --chrome-sm), and on [wrInput] from wrSize to size ' +
+                '(and from [wrSize] to [size]).');
             context.logger.info('Verify the result with `git diff` — a few edge cases may need manual touch-up.');
         }
+        if (leftoverSizes.length > 0) {
+            context.logger.warn(`ngwr v14: \`wrSize\` is still on a [wrInput] field in ${leftoverSizes.length} file(s), in a spelling ` +
+                "the rename did not match. [wrInput]'s input has been `size` since v14, so a static wrSize is " +
+                'ignored — it lands as a plain DOM attribute and the field renders at its default size, with ' +
+                'nothing said — and a bound [wrSize] fails to compile (NG8002). Rename it to `size` by hand.');
+            for (const file of leftoverSizes)
+                context.logger.warn(`  ${file}`);
+        }
         if (staleCatalogs.length > 0) {
             context.logger.warn(`ngwr v14: a translated \`pagination.of\` found in ${staleCatalogs.length} file(s). The range is ` +
                 'one template now — replace it with `pagination.range` ("{{from}}–{{to}} of {{total}}") and ' +
@@ -399,7 +454,8 @@ function ngUpdateV14() {
             i18nProviders.length === 0 &&
             defaultConfigs.length === 0 &&
             ofLabels.length === 0 &&
-            staleCatalogs.length === 0) {
+            staleCatalogs.length === 0 &&
+            leftoverSizes.length === 0) {
             context.logger.info('ngwr v14 migration: nothing to do — no affected usage found.');
         }
         return tree;

package/schematics/migrations/v7/index.js

@@ -6,6 +6,17 @@
  * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+/**
+ * What an open tag may hold before the attribute a rule is after. A quoted value
+ * is consumed only as a PAIR: the plain `[^>]*?` this replaced read a `>` inside
+ * a binding as the end of the tag, so
+ * `<wr-select [placeholder]="n > 0 ? 'a' : 'b'" multi>` kept its `multi` while the
+ * same attributes in the other order moved — and a lone quote is never consumed,
+ * so a rule cannot slide through an apostrophe in one element's value into the
+ * next element. `migration-v14`'s `IN_TAG` carries the full account, including
+ * the one shape this skips: an UNQUOTED value holding a quote (`title=it's`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 const HTML_TRANSFORMS = [
     // wr-autocomplete → wr-select mode="search"
     { pattern: /<wr-autocomplete(\s|>|\/)/g, replacement: '<wr-select mode="search"$1' },
@@ -35,9 +46,9 @@ const HTML_TRANSFORMS = [
     { pattern: /<wr-count-up-text(\s|>|\/)/g, replacement: '<wr-count-up$1' },
     { pattern: /<\/wr-count-up-text>/g, replacement: '</wr-count-up>' },
     // wr-select's deprecated [multi] alias → mode="multi"
-    { pattern: /(<wr-select\b[^>]*?)\s\[multi\]="true"/g, replacement: '$1 mode="multi"' },
-    { pattern: /(<wr-select\b[^>]*?)\s\[multi\]="false"/g, replacement: '$1' },
-    { pattern: /(<wr-select\b[^>]*?)\smulti(?=[\s>/])/g, replacement: '$1 mode="multi"' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\s\[multi\]="true"`, 'g'), replacement: '$1 mode="multi"' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\s\[multi\]="false"`, 'g'), replacement: '$1' },
+    { pattern: new RegExp(String.raw `(<wr-select\b${IN_TAG})\smulti(?=[\s>/])`, 'g'), replacement: '$1 mode="multi"' },
     // wr-image → wr-lightbox (rename — same surface)
     { pattern: /<wr-image(\s|>|\/)/g, replacement: '<wr-lightbox$1' },
     { pattern: /<\/wr-image>/g, replacement: '</wr-lightbox>' },
@@ -46,7 +57,7 @@ const HTML_TRANSFORMS = [
     // attribute form (`<h1 wr-animated-text …>`) has no 1:1 target and is
     // left for manual migration; a bound `[mode]` falls back to typewriter.
     {
-        pattern: /<wr-animated-text\b([^>]*?)\s*(\/>|>\s*<\/wr-animated-text>)/g,
+        pattern: new RegExp(String.raw `<wr-animated-text\b(${IN_TAG})\s*(\/>|>\s*<\/wr-animated-text>)`, 'g'),
         replacement: (_match, attrs) => {
             const mode = /\bmode\s*=\s*"(\w+)"/.exec(attrs)?.[1] ?? 'typewriter';
             const tag = mode === 'split' ? 'wr-split-text' : mode === 'scramble' ? 'wr-decrypt-text' : 'wr-typewriter';

package/schematics/migrations/v8/index.js

@@ -12,6 +12,17 @@ const DENSITY_MAP = [
     ['default', 'md'],
     ['comfortable', 'lg'],
 ];
+/**
+ * What an open tag may hold before the attribute a rule is after. A quoted value
+ * is consumed only as a PAIR: the plain `[^>]*?` this replaced read a `>` inside
+ * a binding as the end of the tag, so `<wr-pagination [disabled]="n > 0" size="xs" />`
+ * kept its `xs` while the same attributes in the other order moved — and a lone
+ * quote is never consumed, so a rule cannot slide through an apostrophe in one
+ * element's value into the next element. `migration-v14`'s `IN_TAG` carries the
+ * full account, including the one shape this skips: an UNQUOTED value holding a
+ * quote (`title=it's`).
+ */
+const IN_TAG = String.raw `(?:"[^"]*"|'[^']*'|[^>"'])*?`;
 const HTML_TRANSFORMS = [
     // density — directive attribute, string form: wrDensity="compact" → "sm"
     ...DENSITY_MAP.map(([from, to]) => ({
@@ -29,8 +40,8 @@ const HTML_TRANSFORMS = [
         replacement: `$1${to}$2`,
     })),
     // pagination size — scoped to the element so other `size="xs"` attrs are untouched
-    { pattern: /(<wr-pagination\b[^>]*?\ssize=")xs(")/g, replacement: '$1sm$2' },
-    { pattern: /(<wr-pagination\b[^>]*?\ssize=")xl(")/g, replacement: '$1lg$2' },
+    { pattern: new RegExp(String.raw `(<wr-pagination\b${IN_TAG}\ssize=")xs(")`, 'g'), replacement: '$1sm$2' },
+    { pattern: new RegExp(String.raw `(<wr-pagination\b${IN_TAG}\ssize=")xl(")`, 'g'), replacement: '$1lg$2' },
 ];
 const TS_TRANSFORMS = [
     // density — provideWrDensity({ defaultDensity: 'compact' }) → 'sm'

package/schematics/migrations/v9/index.js

@@ -14,17 +14,26 @@ Object.defineProperty(exports, "__esModule", { value: true });
  * `FormValueControl`) and must be left alone — renaming it would break every
  * bound group.
  *
- * Quoted values are STEPPED OVER rather than excluded, and that is the half a
- * plain `[^>]*?` got wrong for two majors: a `>` inside a binding expression
- * looks like the end of the tag, so `<wr-checkbox [disabled]="n > 0" value="a">`
- * kept its `value` while the same attributes in the other order moved. The
- * leftover is SILENT — a static `value="a"` that matches no input is an ordinary
- * DOM attribute, `strictTemplates` says nothing, and every checkbox in the group
- * keeps the default identity `null`, so they all toggle together. That is the
- * exact defect this migration exists to prevent, reintroduced by the migration
- * itself. `migration-v14` fixed the same anchoring; this is that fix, ported.
+ * A quoted value is consumed only as a PAIR, and both halves of that matter.
+ * Stepping OVER it is what a plain `[^>]*?` got wrong for two majors: a `>`
+ * inside a binding expression looks like the end of the tag, so
+ * `<wr-checkbox [disabled]="n > 0" value="a">` kept its `value` while the same
+ * attributes in the other order moved. The leftover is SILENT — a static
+ * `value="a"` that matches no input is an ordinary DOM attribute,
+ * `strictTemplates` says nothing, and every checkbox in the group keeps the
+ * default identity `null`, so they all toggle together. That is the exact defect
+ * this migration exists to prevent, reintroduced by the migration itself.
+ *
+ * Never consuming a LONE quote is the half the first fix missed. It spelled the
+ * fallback `[^>]`, which matches a quote too, so the engine could backtrack into
+ * a single-quoted span starting at the apostrophe of `label="it's"` and running
+ * past `/>` into the next element: `<wr-checkbox label="it's" />` followed by
+ * `<wr-select [x]="'y'" value="z" />` renamed the SELECT's form model. Now a rename
+ * stays inside one open tag whenever every quote in it opens or closes a value;
+ * an UNQUOTED value holding a quote (`title=it's`) breaks that, and is skipped.
+ * `migration-v14`'s `IN_TAG` carries the same pattern and the longer account.
  */
-const CHECKBOX_TAG = String.raw `<wr-checkbox(?![-\w])(?:"[^"]*"|'[^']*'|[^>])*?\s`;
+const CHECKBOX_TAG = String.raw `<wr-checkbox(?![-\w])(?:"[^"]*"|'[^']*'|[^>"'])*?\s`;
 const HTML_TRANSFORMS = [
     // <wr-checkbox … value="x">  →  checkboxValue="x"
     { pattern: new RegExp(`(${CHECKBOX_TAG})value=`, 'g'), replacement: '$1checkboxValue=' },

package/schematics/use/symbol-map.json

@@ -91,6 +91,8 @@
   "WrGauge": "ngwr/gauge",
   "WrGlitchText": "ngwr/glitch-text",
   "WrGradientText": "ngwr/gradient-text",
+  "WrGraph": "ngwr/graph",
+  "WrGraphNodeTemplate": "ngwr/graph",
   "WrHotkey": "ngwr/hotkey",
   "WrHotkeyBinding": "ngwr/hotkey",
   "WrI18n": "ngwr/i18n",

package/segmented/styles/_index.scss

@@ -70,6 +70,14 @@
     transition: transform 0.25s var(--wr-ease-out);
   }
 
+  // A direction flip mirrors the strip, which moves the thumb's slot by the whole
+  // width of it. Animated, that drags the pill across options it does not mark;
+  // the component sets this class for the tick the flip lands in so the pill is
+  // simply already there. Selection changes keep their slide.
+  &--flipping &__thumb {
+    transition: none;
+  }
+
   &--unselected &__thumb {
     opacity: 0;
   }

package/skills/ngwr/SKILL.md

@@ -5,7 +5,7 @@ description: Build Angular UIs with the ngwr component library (standalone, sign
 
 # ngwr
 
-An Angular 22 UI library: 225 tree-shakable entry points, 112 of them shipping a selector.
+An Angular 22 UI library: 227 tree-shakable entry points, 113 of them shipping a selector.
 Standalone, signals-first, zoneless, `ViewEncapsulation.None`. One runtime
 dependency (`tslib`).
 
@@ -44,8 +44,13 @@ guess gets backwards.
 - **There is no `ControlValueAccessor`.** Value components implement Signal
   Forms' `FormValueControl` / `FormCheckboxControl`. Bind
   `[formField]="form.x"`, or use the two-way model standalone —
-  `[(value)]`, `[(checked)]`. `[(ngModel)]` and reactive forms still work:
-  Angular 22 synthesises the accessor.
+  `[(value)]`, `[(checked)]`. `[(ngModel)]` and reactive forms still bind,
+  with no accessor created: Angular's `NgModel` / `FormControlDirective` drive
+  the `value` or `checked` model directly. That bridge does NOT apply template
+  validator directives — `required`, `minlength`, `maxlength`, `pattern` or
+  `email` on an ngwr control is silently ignored and the form submits — so put
+  validators on the `FormControl`. It also ignores `updateOn`, and a
+  `{ emitEvent: false }` write needs `markForCheck()`.
 - **`<wr-checkbox>` group identity is `checkboxValue`, not `value`.**
   `value` is reserved for the form value, so a leftover `value="x"` lands on the
   host as a plain DOM attribute, every box in the group keeps the default
@@ -95,8 +100,8 @@ cause.
 - `provideWrLoadingBarRouter() // from 'ngwr/loading-bar/router'`
   — without it the bar never responds to navigation; it only moves for manual start() / complete()
   — needed by: `WrLoadingBar`
-- `provideWrI18n() + provideWrI18nStaticLoader({ en: wrEn }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
-  — the pipe and directive read from a catalog you provide
+- `provideWrI18n() + provideWrI18nBaseCatalogs({ en: wrEn }) + provideWrI18nStaticLoader({ en: { … } }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
+  — the pipe and directive read from a catalog you provide. Register ngwr's with `provideWrI18nBaseCatalogs`, never spread it into yours: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key
   — needed by: `WrTPipe`, `WrTDirective`, `WrI18n`
 
 ## Testing

package/skills/ngwr/references/catalog.md

@@ -89,6 +89,8 @@ root barrel for components.
 | `ngwr/glitch-text/testing` | `import { WrGlitchTextHarness } from 'ngwr/glitch-text/testing'` | — |
 | `ngwr/gradient-text` | `import { WrGradientText } from 'ngwr/gradient-text'` | `wr-gradient-text` |
 | `ngwr/gradient-text/testing` | `import { WrGradientTextHarness } from 'ngwr/gradient-text/testing'` | — |
+| `ngwr/graph` | `import { WrGraph } from 'ngwr/graph'` | `ng-template[wrGraphNode]` `wr-graph` |
+| `ngwr/graph/testing` | `import { WrGraphHarness } from 'ngwr/graph/testing'` | — |
 | `ngwr/hotkey` | `import { WrHotkey } from 'ngwr/hotkey'` | `[wrHotkey]` |
 | `ngwr/i18n` | `import { WrI18n } from 'ngwr/i18n'` | `[wrT]` |
 | `ngwr/i18n/ar` | `import { wrAr } from 'ngwr/i18n/ar'` | — |

package/skills/ngwr/references/setup.md

@@ -60,9 +60,9 @@ Every date mode goes through an adapter; there is no built-in default. Needed by
 
 Without it the bar never responds to navigation; it only moves for manual start() / complete(). Needed by `WrLoadingBar`.
 
-### `provideWrI18n() + provideWrI18nStaticLoader({ en: wrEn }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
+### `provideWrI18n() + provideWrI18nBaseCatalogs({ en: wrEn }) + provideWrI18nStaticLoader({ en: { … } }) // from 'ngwr/i18n' + 'ngwr/i18n/en'`
 
-The pipe and directive read from a catalog you provide. Needed by `WrTPipe`, `WrTDirective`, `WrI18n`.
+The pipe and directive read from a catalog you provide. Register ngwr's with `provideWrI18nBaseCatalogs`, never spread it into yours: a spread is shallow, so any namespace you share with ngwr, e.g. `common`, `validation`, `table`, keeps only the side spread last, and the other side's keys stop resolving with nothing logged — ngwr's components fall back to English and a `wrT` read of a lost key renders the raw key. Needed by `WrTPipe`, `WrTDirective`, `WrI18n`.
 
 ## Optional, app-wide
 

package/styles.scss

@@ -61,6 +61,7 @@
 @forward './gauge/styles';
 @forward './glitch-text/styles';
 @forward './gradient-text/styles';
+@forward './graph/styles';
 @forward './icon/styles';
 @forward './image-cropper/styles';
 @forward './input/styles';

package/table/styles/_index.scss

@@ -389,6 +389,14 @@
     padding: 0;
     cursor: pointer;
     color: inherit;
+    // The indicator inside is a bare `.wr-icon__svg`, which is `1em`, and a
+    // `<button>` does not inherit its font-size: it takes the browser's control
+    // font (about 13.33px) unless the app resets it. So the same glyph measured
+    // 13.33px on a page with no reset and 12px under `ngwr/reset`, which sets
+    // `font: inherit`. Inheriting the size makes `1em` the header's own text in
+    // every app. `--wr-icon-size` cannot do this job — only a `<wr-icon>` host
+    // reads it, and the rule here used to set it for nothing.
+    font-size: inherit;
     line-height: 0;
   }
 
@@ -741,21 +749,35 @@
 
 .wr-table-sort {
   display: inline-flex;
-  --wr-icon-size: 0.875rem;
+  // Unsorted is the flat line the template draws, at full strength in the muted
+  // role — the same ink as the filter funnel beside it. It used to be the sort
+  // ARROW at half opacity, which is how an unsorted column came to read as
+  // "sorted ascending, dimmed". The glyph carries the state now, so the opacity
+  // has no job left, and dropping it is what lifts the indicator over the 3:1 a
+  // graphic that identifies a control is held to. Measured on the header's own
+  // background in Chromium, after the colour transition settled: from 1.98:1 to
+  // 4.78:1 in light (`#5f6c7d` on `#eff2f6`) and from 2.74:1 to 7.04:1 in dark
+  // (`#9aa6b8` on `#131a2b`). An SVG stroke is invisible to axe, so re-measure
+  // by hand if this ink or the header fill ever moves.
   color: var(--wr-color-on-surface-muted);
-  transition:
-    transform var(--wr-transition-base),
-    color var(--wr-transition-base);
-  opacity: 0.5;
-
-  &--asc {
-    opacity: 1;
+  // Only the colour eases back to unsorted. A transition is taken from the
+  // state being ENTERED, so leaving `--desc` for the base would otherwise spin
+  // the flat line from 180deg to 0 — motion with no direction to report. The
+  // turn between the two arrows still animates, since both modifiers carry it.
+  transition: color var(--wr-transition-base);
+
+  // The template swaps the glyph — a flat line while unsorted, an arrow here
+  // (table-sort.ts) — so the state reads from the shape, and the primary ink
+  // only says which column is the sorted one.
+  &--asc,
+  &--desc {
     color: var(--wr-color-primary);
+    transition:
+      transform var(--wr-transition-base),
+      color var(--wr-transition-base);
   }
 
   &--desc {
-    opacity: 1;
-    color: var(--wr-color-primary);
     transform: rotate(180deg);
   }
 }
@@ -781,7 +803,13 @@
     padding: 0;
     cursor: pointer;
     color: inherit;
-    --wr-icon-size: 0.875rem;
+    // The funnel is the same bare `1em` svg as the sort indicator beside it, in
+    // the same kind of `<button>`, so it inherits the header's font-size for the
+    // same reason (see `.wr-table__sort-btn`). The size only, not the `font`
+    // shorthand: that would also bring the header's 1.25rem line-height, and the
+    // count pill beside the funnel — 10px type with no line-height of its own —
+    // grows from 12px to 20px tall under it.
+    font-size: inherit;
   }
 
   &__count {
@@ -855,7 +883,6 @@
     border-radius: var(--wr-border-radius-sm);
     border: 1px solid var(--wr-color-outline);
     color: transparent;
-    --wr-icon-size: 0.75rem;
     transition: var(--wr-transition-base);
   }
 

package/theme/styles/_focus.scss

@@ -164,3 +164,10 @@
 .wr-alert__close:focus-visible {
   @include focus-ring;
 }
+
+// Graph viewport — the scroller is the graph's one tab stop, so a keyboard user
+// scrolling it needs to see where focus is. Safe as an OUTSET ring: the outline
+// sits outside the scroller's own box, and `.wr-graph` sets no `overflow`.
+.wr-graph__viewport:focus-visible {
+  @include focus-ring;
+}

package/types/ngwr-cascader.d.ts

@@ -133,6 +133,13 @@ declare class WrCascader<T = string> implements FormValueControl<unknown> {
     private readonly scrollStrategies;
     private readonly destroyRef;
     private readonly injector;
+    /**
+     * Ambient reading direction, for the open panel alone — nothing in this
+     * component reads it directly. Optional so a bare `TestBed` needs no
+     * provider; `Directionality` is root-provided anyway, and a missing one
+     * simply reads as `ltr`.
+     */
+    private readonly dir;
     private overlayRef;
     constructor();
     protected onTriggerClick(): void;

package/types/ngwr-color-picker.d.ts

@@ -415,6 +415,14 @@ declare class WrColorPickerTrigger {
     private readonly vcr;
     private readonly scrollStrategies;
     private readonly destroyRef;
+    private readonly injector;
+    /**
+     * Ambient reading direction, for the open panel alone — nothing in this
+     * directive reads it directly. Optional so a bare `TestBed` needs no
+     * provider; `Directionality` is root-provided anyway, and a missing one
+     * simply reads as `ltr`.
+     */
+    private readonly dir;
     protected readonly isOpen: _angular_core.WritableSignal<boolean>;
     private overlayRef;
     /** @internal Public so the host binding can read it. */

package/types/ngwr-context-menu.d.ts

@@ -44,9 +44,18 @@ declare class WrContextMenu {
     readonly menu: _angular_core.InputSignal<WrContextMenuPanel>;
     private readonly host;
     private readonly overlay;
+    /**
+     * The reading direction the open menu has to keep up with.
+     *
+     * Optional inject, as on every other overlay here: `Directionality` is
+     * root-provided and so never null in an app, but a bare `TestBed` that
+     * provides nothing should still get a menu that opens.
+     */
+    private readonly dir;
     private readonly outsideClick;
     private readonly vcr;
     private readonly scrollStrategies;
+    private readonly injector;
     private readonly destroyRef;
     /**
      * Id of the menu element while this trigger's menu is open, published on the
@@ -219,6 +228,7 @@ declare class WrContextMenuItem {
     private readonly dir;
     private readonly vcr;
     private readonly scrollStrategies;
+    private readonly injector;
     private readonly destroyRef;
     private submenuRef;
     private submenuKeys;

package/types/ngwr-date-picker.d.ts

@@ -83,6 +83,14 @@ declare class WrDatePicker implements FormValueControl<Date | null> {
     private readonly scrollStrategies;
     private readonly host;
     private readonly destroyRef;
+    private readonly injector;
+    /**
+     * Ambient reading direction, for the open panel alone — nothing in this
+     * component reads it directly. Optional so a bare `TestBed` needs no
+     * provider; `Directionality` is root-provided anyway, and a missing one
+     * simply reads as `ltr`.
+     */
+    private readonly dir;
     protected readonly inputEl: _angular_core.Signal<ElementRef<HTMLInputElement>>;
     protected readonly triggerEl: _angular_core.Signal<ElementRef<HTMLButtonElement> | undefined>;
     /** The picked Date. Bound by `[formField]`, or two-way via `[(value)]`. */
@@ -306,6 +314,14 @@ declare class WrDateRangePicker implements FormValueControl<WrDateRange | null>
     private readonly scrollStrategies;
     private readonly host;
     private readonly destroyRef;
+    private readonly injector;
+    /**
+     * Ambient reading direction, for the open panel alone — nothing in this
+     * component reads it directly. Optional so a bare `TestBed` needs no
+     * provider; `Directionality` is root-provided anyway, and a missing one
+     * simply reads as `ltr`.
+     */
+    private readonly dir;
     protected readonly startEl: _angular_core.Signal<ElementRef<HTMLInputElement>>;
     protected readonly endEl: _angular_core.Signal<ElementRef<HTMLInputElement>>;
     protected readonly triggerEl: _angular_core.Signal<ElementRef<HTMLButtonElement> | undefined>;

package/types/ngwr-dialog.d.ts

@@ -149,6 +149,7 @@ declare class WrDialog {
     private readonly isBrowser;
     private readonly responsiveConfig;
     private readonly i18n;
+    private readonly dir;
     private readonly location;
     open<C, R = unknown, D = unknown>(component: ComponentType<C>, options?: WrDialogOptions<D>): WrDialogRef<C, R>;
     /**