@koobiq/components 20.4.2 → 21.0.0

package/schematics/migrations/splitter-deprecated-path/README.md

@@ -0,0 +1,136 @@
+# splitter-deprecated-path
+
+Migration schematic invoked automatically by `ng update @koobiq/components@20`
+(registered for `20.3.0-0`). Rewrites `@koobiq/components/splitter` imports to
+`@koobiq/components/splitter/deprecated`.
+
+## Background
+
+`@koobiq/components/splitter` now resolves to a rewritten splitter that lays its panels out with
+CSS grid and adds per-panel size constraints, collapsing and hiding, snap points, full keyboard
+support and the WAI-ARIA `separator` pattern. The previous implementation — `KbqSplitterComponent`
+with `KbqSplitterAreaDirective`, `KbqGutterDirective`, `KbqGutterGhostDirective`,
+`KbqSplitterModule` and the `Direction` enum — moved to `@koobiq/components/splitter/deprecated`
+and will be removed in 22.0.0.
+
+Nothing about that implementation changed: `direction`, `disabled`, `useGhost`, `hideGutters`,
+`gutterSize`, `gutterPositionChange`, the `[kbq-splitter-area]` attribute selector and the
+`min-width` / `min-height` driven constraints all behave exactly as before at the new path.
+Rewriting the import is the whole migration — adopting the new splitter is a separate, manual step.
+
+## Behaviour change
+
+Most unmigrated imports break loudly: `KbqSplitterComponent`, `KbqSplitterAreaDirective`,
+`KbqGutterDirective`, `KbqGutterGhostDirective` and `Direction` live at the `/deprecated` path
+only, so the build stops with `TS2305: … has no exported member`.
+
+`KbqSplitterModule` is the silent one — both entry points export a class under that name, and so
+does the `kbq-splitter` element selector exist on both sides. An unmigrated
+`import { KbqSplitterModule } from '@koobiq/components/splitter'` therefore keeps compiling, but
+now pulls in the rewritten splitter, which projects `kbq-splitter-panel` children instead of
+`[kbq-splitter-area]` hosts and takes `orientation` rather than `direction`. Such a group renders
+its content with no panels and no separators. This is the case the migration exists for.
+
+Templates need no changes of their own: once the import points at `/deprecated`, `<kbq-splitter>`
+with `[kbq-splitter-area]` hosts, `direction`, `useGhost`, `hideGutters` and `gutterSize` keeps
+working exactly as before.
+
+## What it does
+
+The schematic walks every `.ts` file under the project root — the whole workspace when `--project`
+is omitted, which is how `ng update` invokes it — skipping `node_modules` and `dist`, and rewrites
+the module specifier `@koobiq/components/splitter` to `@koobiq/components/splitter/deprecated`.
+
+The match is quote-anchored (`(['"])@koobiq/components/splitter\1`), so only the exact, bare
+specifier is taken, in the quote style it was written in:
+
+| Specifier                                        | Result                                                                                 |
+| ------------------------------------------------ | -------------------------------------------------------------------------------------- |
+| `'@koobiq/components/splitter'`                  | rewritten, still single-quoted                                                         |
+| `"@koobiq/components/splitter"`                  | rewritten, still double-quoted                                                         |
+| `'@koobiq/components/splitter/deprecated'`       | untouched — the migration is idempotent                                                |
+| `'@koobiq/components/splitter-x'` (hypothetical) | untouched — the closing quote is required, so a longer specifier is not a prefix match |
+
+It is a textual replacement rather than an AST rewrite, so an `import`, an `export … from`, a
+dynamic `import()` and a specifier handed to something like `jest.mock()` are all covered by the
+same pass.
+
+## What it does _not_ do (manual)
+
+| Pattern                          | Manual migration                                                                                                                                                                         |
+| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| A specifier outside a `.ts` file | Only `.ts` files are visited — the same string in a JSON config or a documentation snippet stays as written                                                                              |
+| Templates                        | `[kbq-splitter-area]` hosts, `direction`, `useGhost`, `hideGutters` and `gutterSize` bindings are left as written; they keep working against the deprecated component at its new path    |
+| Moving off `/deprecated`         | Nothing is migrated _to_ the new splitter: areas become `kbq-splitter-panel`, `direction` becomes `orientation`, sizes move from `min-width` / CSS `flex` onto `size` / `minSize` inputs |
+
+`fix` defaults to `true`. `ng update` invokes migrations with no options at all, and
+`migrations.json` declares no schema, so the rule applies that default itself. With `--fix false`
+every file that would change is logged instead of written, followed by the same count either way.
+
+[Params](schema.ts)
+
+Usage for Angular Cli:
+
+```shell
+ng g @koobiq/components:splitter-deprecated-path --project "<your project>"
+```
+
+Usage for Nx:
+
+```shell
+nx g @koobiq/components:splitter-deprecated-path --project "<your project>"
+```
+
+### Run locally
+
+Build package
+
+```shell
+yarn run build:schematics
+```
+
+Run command (for example, for `koobiq-docs` project)
+
+```shell
+ng g ./dist/components/schematics/collection.json:splitter-deprecated-path --project koobiq-docs
+```
+
+### Result
+
+#### Before
+
+```ts
+import { Component } from '@angular/core';
+import { KbqSplitterModule } from '@koobiq/components/splitter';
+
+@Component({
+    selector: 'my-page',
+    imports: [KbqSplitterModule],
+    template: `
+        <kbq-splitter [useGhost]="true">
+            <div kbq-splitter-area>...</div>
+            <div kbq-splitter-area>...</div>
+        </kbq-splitter>
+    `
+})
+export class MyPage {}
+```
+
+#### After
+
+```ts
+import { Component } from '@angular/core';
+import { KbqSplitterModule } from '@koobiq/components/splitter/deprecated';
+
+@Component({
+    selector: 'my-page',
+    imports: [KbqSplitterModule],
+    template: `
+        <kbq-splitter [useGhost]="true">
+            <div kbq-splitter-area>...</div>
+            <div kbq-splitter-area>...</div>
+        </kbq-splitter>
+    `
+})
+export class MyPage {}
+```

package/schematics/migrations/splitter-deprecated-path/index.js

@@ -0,0 +1,20 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_deprecatedPathMigration = require('../../utils/deprecated-path-migration.js');
+require('../../utils/messages.js');
+require('../../package-config-BhU2TfC8.js');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+/**
+ * `@koobiq/components/splitter` now resolves to the rewritten splitter — the `flex-basis` based
+ * component it used to export (`KbqSplitterComponent`, `KbqSplitterAreaDirective`,
+ * `KbqGutterDirective`, `KbqGutterGhostDirective`, `KbqSplitterModule`, `Direction`) moved to
+ * `@koobiq/components/splitter/deprecated`. This rewrites the import specifier only; the API itself
+ * is unchanged at its new path.
+ */
+var index = utils_deprecatedPathMigration.deprecatedPathMigration('splitter');
+
+exports.default = index;

package/schematics/migrations/splitter-deprecated-path/schema.json

@@ -0,0 +1,20 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-splitter-deprecated-path",
+    "title": "Koobiq components splitter deprecated-path rewrite",
+    "type": "object",
+    "properties": {
+        "project": {
+            "type": "string",
+            "description": "Name of the project to migrate. If omitted, the migration runs over the whole tree.",
+            "$default": {
+                "$source": "projectName"
+            }
+        },
+        "fix": {
+            "type": "boolean",
+            "default": true,
+            "description": "When true, applies all auto-fix replacements. When false, prints what would change without writing."
+        }
+    }
+}

package/schematics/migrations/state-saving-default/README.md

@@ -0,0 +1,67 @@
+# state-saving-default
+
+Migration schematic invoked automatically by `ng update @koobiq/components@20`
+(registered for `21.0.0-0`). Reports the consequences of `kbq-tab-group`, `kbq-sidebar` and
+`kbq-content-panel-container` persisting the state a user changes, with `useStateSaving` defaulting to
+`true` on all three. It never writes to the tree.
+
+## Background
+
+All three gained the same state saving the accordion and the tree already have, applied through the
+`KbqStateSaving` host directive, and it is on by default. With no `stateSavingKey` the key is derived from
+where the component sits in the document — the chain of tag names up to `<body>`, cut short by the first
+author-written `id`, which becomes the anchor.
+
+Each of them keeps out of the store while the application drives the state, so the change only reaches
+markup that says nothing about it:
+
+| Component                     | Persists                                                 | Stays out of it while                            |
+| ----------------------------- | -------------------------------------------------------- | ------------------------------------------------ |
+| `kbq-tab-group`               | the selected tab, by `tabId` and by position             | `selectedIndex` or `activeTab` is bound          |
+| `kbq-sidebar`                 | whether it was open, and the width it was last closed at | `opened` is bound                                |
+| `kbq-content-panel-container` | whether it was open, and the dragged width               | `opened` is bound — the width is restored anyway |
+
+## What it reports
+
+- **The default flip**, once per component, for a file that renders one and neither opts out nor binds
+  the state the application would own.
+- **Tabs with no `tabId`.** The selection then falls back to the position, which survives a reload but
+  not a reordering; a dev-mode warning says so at runtime too.
+- **`KbqContentPanelContainer.opened` read programmatically.** It is `openedInput` now and reads
+  `undefined` while nothing binds it, which is how the panel tells a bound `opened` from an unbound one.
+  Templates are unaffected; `isOpened()` is the public read.
+
+Each check is evaluated against the whole file, matching the other warn-only migrations in this
+collection. A file holding two tab groups where only one opts out is not reported — inspect it by hand.
+
+## What it does _not_ do
+
+It does not insert `[useStateSaving]="false"`. The markup whose behaviour changed is exactly the markup
+that says nothing about the input, so opting every component out would be a rewrite of every consumer
+template that also withholds the feature this release is shipping.
+
+It also says nothing about `kbq-tab-nav-bar`, which deliberately never persists: it is the navigation
+variant, where the router decides which link is active and the URL is the state worth restoring.
+
+## Behaviour worth knowing without a report
+
+- **A component rendered inside an overlay does not persist.** It is not in the document when it
+  initializes and so has no stable key.
+- **The content panel's width is restored even when `[opened]` is bound.** There is no `widthChange`
+  output, so a drag never reached the application; `[width]` is the width the panel starts at. A
+  double-click on the resizer restores that declared width, and the reset is persisted too.
+- **The sidebar's width is the one it had when last closed** — the same width it already reuses when
+  reopening. Dragging it wider and reloading without closing keeps the previous width.
+
+## Storage format
+
+Entries are written under a `kbq.state.` prefix and carry a `savedAt` timestamp, so an entry stranded by a
+markup change is collected once it outlives `KBQ_STATE_SAVING_TTL` (90 days by default). Reading an entry
+refreshes it, so state that is visited but never changed does not expire under an active user.
+
+## Related tokens
+
+- `KBQ_STATE_STORE` — where state is persisted. `KbqSessionStorageStateStore` is bundled for state that
+  should live no longer than the tab session.
+- `KBQ_STATE_SAVING_KEY_RESOLVER` — how the key is derived when no `stateSavingKey` is given.
+- `KBQ_STATE_SAVING_TTL` — how long an entry survives without being written or read.

package/schematics/migrations/state-saving-default/data.js

@@ -0,0 +1,88 @@
+'use strict';
+
+/**
+ * Data for the `state-saving-default` migration.
+ *
+ * `KbqTabGroup`, `KbqSidebar` and `KbqContentPanelContainer` persist the state a user changes now, and
+ * `useStateSaving` defaults to `true` on all three. Each of them keeps the state out of the store while
+ * the application drives it — a bound `selectedIndex`/`activeTab`, `opened` on the sidebar, `opened` on
+ * the content panel — so only the markup that says nothing about those is reached by the change.
+ *
+ * Warn-only. The markup whose behaviour changed is exactly the markup that says nothing about the input,
+ * so there is no expression to rewrite — and rewriting it to `[useStateSaving]="false"` would withhold
+ * the feature this release is shipping.
+ */
+/** Import specifiers that mark a file as a consumer of one of the three components. */
+const PACKAGES = [
+    '@koobiq/components/tabs',
+    '@koobiq/components/sidebar',
+    '@koobiq/components/content-panel'
+];
+/** Identifier and element shapes that mark a consumer without an import. */
+const CONSUMER_TYPE = '\\bKbqTabGroup\\b|\\bKbqSidebar\\b|\\bKbqContentPanelContainer\\b|' +
+    '\\bkbq-tab-group\\b|\\bkbq-sidebar\\b|\\bkbq-content-panel-container\\b';
+const TAB_GROUP = '<kbq-tab-group\\b';
+const SIDEBAR = '<kbq-sidebar\\b';
+const CONTENT_PANEL = '<kbq-content-panel-container\\b';
+const warnPatterns = [
+    {
+        anchor: TAB_GROUP,
+        pattern: TAB_GROUP,
+        // A bound selection stays with the application, so those groups are unaffected.
+        unless: '\\buseStateSaving\\b|\\[\\(?selectedIndex\\)?\\]|\\[\\(?activeTab\\)?\\]',
+        message: 'Tab groups remember the selected tab by default now: useStateSaving defaults to true. Pass ' +
+            '[useStateSaving]="false" to keep the previous behaviour. Nothing is persisted while ' +
+            'selectedIndex or activeTab is bound, and kbq-tab-nav-bar never persists — the router owns ' +
+            'which link is active there.'
+    },
+    {
+        anchor: TAB_GROUP,
+        pattern: '<kbq-tab\\b',
+        unless: '\\btabId\\b|\\buseStateSaving\\b|\\[\\(?selectedIndex\\)?\\]|\\[\\(?activeTab\\)?\\]',
+        message: 'These tabs carry no tabId, so the selection is persisted by position. A position survives a ' +
+            'reload but not a reordering, and then restores the wrong tab — a dev-mode warning says so. ' +
+            'Give the tabs a tabId.'
+    },
+    {
+        anchor: SIDEBAR,
+        pattern: SIDEBAR,
+        // `[opened]` means the application decides, and the sidebar then persists nothing.
+        unless: '\\buseStateSaving\\b|\\[opened\\]',
+        message: 'Sidebars remember whether they were open, and the width they were last closed at, by default ' +
+            'now: useStateSaving defaults to true. Pass [useStateSaving]="false" to keep the previous ' +
+            'behaviour. Nothing is persisted while opened is bound.'
+    },
+    {
+        anchor: CONTENT_PANEL,
+        pattern: CONTENT_PANEL,
+        unless: '\\buseStateSaving\\b',
+        message: 'Content panels remember their width, and whether they were open, by default now: ' +
+            'useStateSaving defaults to true. Pass [useStateSaving]="false" to keep the previous ' +
+            'behaviour. The opened state is left alone while [opened] is bound, but the width is restored ' +
+            'either way — there is no widthChange output, so a drag never reached the application anyway.'
+    },
+    {
+        // Programmatic access names the class, which the markup-only anchor does not cover.
+        anchor: '\\bKbqContentPanelContainer\\b',
+        pattern: '\\.\\s*opened\\s*\\(',
+        message: 'KbqContentPanelContainer.opened is now openedInput, and reads undefined rather than false ' +
+            'while nothing binds it — which is how the panel tells a bound opened from an unbound one. ' +
+            'The markup is unchanged; read isOpened() for the state itself.'
+    }
+];
+/** Printed once, after the per-file reports. */
+const SUMMARY = [
+    '  A component rendered inside an overlay does not persist: it is not in the document when it',
+    '  initializes and so has no stable key. The key otherwise comes from stateSavingKey, or is derived',
+    '  from the position in the document when none is given.',
+    '  Storage format: entries are written under a "kbq.state." prefix and carry a timestamp, so an',
+    '  entry stranded by a markup change is collected once it outlives KBQ_STATE_SAVING_TTL (90 days by',
+    '  default).',
+    '  Provide KBQ_STATE_STORE to persist somewhere else (KbqSessionStorageStateStore is bundled), and',
+    '  KBQ_STATE_SAVING_KEY_RESOLVER to derive the key from something other than the document position.'
+];
+
+exports.CONSUMER_TYPE = CONSUMER_TYPE;
+exports.PACKAGES = PACKAGES;
+exports.SUMMARY = SUMMARY;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/state-saving-default/index.js

@@ -0,0 +1,62 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_messages = require('../../utils/messages.js');
+var utils_packageConfig = require('../../package-config-BhU2TfC8.js');
+var migrations_stateSavingDefault_data = require('./data.js');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const LABEL = '[state-saving-default]';
+const EXTENSIONS = ['.ts', '.html'];
+/** A file is a consumer if it imports one of the packages, names a component, or renders one. */
+function referencesConsumer(content) {
+    return migrations_stateSavingDefault_data.PACKAGES.some((name) => content.includes(name)) || new RegExp(migrations_stateSavingDefault_data.CONSUMER_TYPE).test(content);
+}
+/**
+ * Reports the consequences of the tab group, the sidebar and the content panel persisting the state a
+ * user changes, with `useStateSaving` defaulting to `true`. Never writes: the markup whose behaviour
+ * changed is exactly the markup that does not mention the input, and rewriting it to opt out would
+ * withhold the feature the release is shipping.
+ *
+ * `.html` is visited as well as `.ts`, because most reports key off the rendered element rather than off
+ * an import.
+ */
+function stateSavingDefault(options) {
+    return async (tree, context) => {
+        const { project } = options;
+        const projectDefinition = await utils_packageConfig.setupOptions(project, tree);
+        const root = projectDefinition?.root ?? '';
+        const rootDir = root ? tree.getDir(root) : tree.root;
+        let consumers = 0;
+        let reported = 0;
+        utils_packageConfig.visitProjectFiles(rootDir, (filePath, entry) => {
+            if (!EXTENSIONS.some((extension) => filePath.endsWith(extension)))
+                return;
+            const content = entry?.content.toString();
+            if (!content || !referencesConsumer(content))
+                return;
+            consumers++;
+            for (const { anchor, pattern, unless, message } of migrations_stateSavingDefault_data.warnPatterns) {
+                if (!new RegExp(anchor).test(content) || !new RegExp(pattern).test(content))
+                    continue;
+                if (unless && new RegExp(unless).test(content))
+                    continue;
+                reported++;
+                utils_messages.logMessage(context.logger, [`${LABEL} ${filePath}`, `  ${message}`]);
+            }
+        });
+        // Nothing here renders one of the three, so the summary would only be noise.
+        if (consumers === 0)
+            return;
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed kbq-tab-group, kbq-sidebar and kbq-content-panel-container under ` +
+                `"${root || '<workspace root>'}", ${consumers} file(s) reference them, ` +
+                `${reported} report(s) raised.`,
+            ...migrations_stateSavingDefault_data.SUMMARY
+        ]);
+    };
+}
+
+exports.default = stateSavingDefault;

package/schematics/migrations/state-saving-default/schema.json

@@ -0,0 +1,15 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-state-saving-default",
+    "title": "Koobiq components state saving default migration",
+    "type": "object",
+    "properties": {
+        "project": {
+            "type": "string",
+            "description": "Name of the project to inspect. If omitted, the migration runs over the whole tree.",
+            "$default": {
+                "$source": "projectName"
+            }
+        }
+    }
+}

package/schematics/migrations/table-cell-content/README.md

@@ -0,0 +1,55 @@
+# table-cell-content
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21`
+(registered for `21.0.0-0`). Reports the removal of `KbqTableCellContent` and the style-surface changes
+the table review made. It never writes to the tree.
+
+## Background
+
+`KbqTableCellContent` was declared `selector: 'kbq-table td'`. Angular's directive selector grammar has
+element names, attributes, classes and `:not(…)` — and no combinators. Its parser calls `setElement()`
+for every bare tag it meets, so the second tag overwrote the first and the effective selector was `td`.
+Two things followed. Every template that imported `KbqTableModule` got a directive instance plus a live
+content query on **every** cell it rendered, whether or not the table was a `kbq-table`. And the
+`kbq-table` element the selector named has never existed: the component is an attribute on a native
+`<table>`.
+
+The one rule the directive fed — a cell holding a button keeps the row at the button's own height — is
+CSS now:
+
+```scss
+.kbq-table > :is(tbody, tfoot) > tr > :is(td, th):has(.kbq-button, .kbq-button-icon) {
+    padding-block: var(--kbq-size-xxs);
+}
+```
+
+That also drops the `@koobiq/components/button` dependency from the table entry point.
+
+| Pattern                     | Manual migration                                                  |
+| --------------------------- | ----------------------------------------------------------------- |
+| `KbqTableCellContent`       | Delete it from the `imports` array; nothing replaces it           |
+| `kbq-table-cell_has-button` | Select the cell: `:is(td, th):has(.kbq-button, .kbq-button-icon)` |
+
+## What else changed
+
+- Row hover and the pill corner radii cover `<th>` inside `<tbody>` as well as `<td>`, so a row led by a
+  row header is highlighted and rounded as a unit. A consumer rule that switched the highlight off per
+  row (`tr:hover { background: none }`) used to be a no-op against the cell-level color — bind
+  `[disableHover]` or set `--kbq-table-states-hover-background: transparent`.
+- Every color is behind a `--kbq-table-*` token: `--kbq-table-header-text`, `--kbq-table-body-text`,
+  `--kbq-table-border-color`, `--kbq-table-states-hover-background` and
+  `--kbq-table-sticky-header-background`, whose value is unchanged — the pinned header still takes
+  `--kbq-background-bg`, now through a token a consumer can point at another surface. The row radius
+  is `--kbq-table-size-row-border-radius`.
+- Cell padding and the corner radii are logical properties, and alignment goes through
+  `--kbq-table-cell-text-align` (default `start`), so a table under `dir="rtl"` mirrors.
+- `<tfoot>` gets the library color and typography it was already being padded for.
+- A pinned header publishes its measured height as `--kbq-table-size-sticky-header-height`, used as
+  `scroll-margin-block-start` on the cells and their focusable content so a control scrolled to the top
+  edge does not land under the header (WCAG 2.2 SC 2.4.11).
+
+## Running it manually
+
+```
+ng generate @koobiq/components:table-cell-content --project my-app
+```

package/schematics/migrations/table-cell-content/data.js

@@ -0,0 +1,66 @@
+'use strict';
+
+/**
+ * Data for the `table-cell-content` migration.
+ *
+ * `KbqTableCellContent` is removed. It was declared `selector: 'kbq-table td'`, and Angular's directive
+ * selector grammar has no descendant combinator: the parser calls `setElement()` for every bare tag it
+ * meets, so the second one overwrote the first and the effective selector was `td`. Every template that
+ * imported `KbqTableModule` therefore got a directive instance plus a live content query on every cell
+ * it rendered, `kbq-table` scoping included nothing, and the `kbq-table` element the selector named has
+ * never existed — the component is an attribute on a native `<table>`.
+ *
+ * The single rule the directive fed is CSS now
+ * (`.kbq-table > :is(tbody, tfoot) > tr > :is(td, th):has(.kbq-button, .kbq-button-icon)`), which also drops the
+ * `@koobiq/components/button` dependency from the table entry point.
+ *
+ * Warn-only: an entry in an `imports` array is deleted rather than replaced, and a stylesheet keyed on
+ * the modifier class has to be re-pointed at the cell, which no rewrite can decide.
+ */
+/** Import specifier that marks a file as a table consumer. */
+const TABLE_PACKAGE = '@koobiq/components/table';
+/** Identifier and attribute shapes that mark a consumer without an import. */
+const TABLE_TYPE = '\\bKbqTable\\w*\\b|\\bkbq-table[\\w-]*';
+const warnPatterns = [
+    {
+        anchor: TABLE_TYPE,
+        pattern: '\\bKbqTableCellContent\\b',
+        message: 'KbqTableCellContent was removed. Its selector was `kbq-table td`, which Angular parses as ' +
+            'plain `td` — it matched every cell in every template importing KbqTableModule, and the ' +
+            '`kbq-table` element it named has never existed. Delete it from the imports array; the reduced ' +
+            'padding of a cell holding a button is plain CSS now and needs no directive.'
+    },
+    {
+        anchor: TABLE_TYPE,
+        pattern: 'kbq-table-cell_has-button',
+        message: 'The kbq-table-cell_has-button class is no longer applied — nothing binds it. A stylesheet ' +
+            'keyed on it should select the cell instead: ' +
+            '`.kbq-table > :is(tbody, tfoot) > tr > :is(td, th):has(.kbq-button, .kbq-button-icon)`.'
+    }
+];
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  Row hover and the pill corner radii cover `<th>` inside `<tbody>` as well as `<td>`, so a row led ' +
+        'by a row header is highlighted and rounded as a unit instead of from its second cell on. A ' +
+        'consumer rule that switched the highlight off per row (`tr:hover { background: none }`) used to ' +
+        'be a no-op against the cell-level color; bind [disableHover] or set ' +
+        '--kbq-table-states-hover-background: transparent instead.',
+    '  Every color is behind a --kbq-table-* token now (--kbq-table-header-text, --kbq-table-body-text, ' +
+        '--kbq-table-border-color, --kbq-table-states-hover-background, --kbq-table-sticky-header-background), ' +
+        'and the row radius is --kbq-table-size-row-border-radius. Overriding the global tokens the theme ' +
+        'used to read directly no longer reaches the table alone.',
+    '  Cell padding and the corner radii are logical properties, and alignment goes through ' +
+        '--kbq-table-cell-text-align (default `start`), so a table under dir="rtl" mirrors instead of ' +
+        'staying left-aligned, and a column can be re-aligned with a custom property instead of ' +
+        'out-specifying `.kbq-table > thead > tr > th`.',
+    '  `<tfoot>` gets the library color and typography it was already being padded for.',
+    '  A pinned header publishes its measured height as --kbq-table-size-sticky-header-height and the ' +
+        'table uses it as scroll-margin-block-start on its cells and their focusable content, so a control ' +
+        'scrolled to the top edge does not land under the header (WCAG 2.2 SC 2.4.11). Add ' +
+        'scroll-padding-block-start to your own scroll container if it holds more than the table.'
+];
+
+exports.SUMMARY = SUMMARY;
+exports.TABLE_PACKAGE = TABLE_PACKAGE;
+exports.TABLE_TYPE = TABLE_TYPE;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/table-cell-content/index.js

@@ -0,0 +1,66 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_messages = require('../../utils/messages.js');
+var utils_packageConfig = require('../../package-config-BhU2TfC8.js');
+var migrations_tableCellContent_data = require('./data.js');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const LABEL = '[table-cell-content]';
+const EXTENSIONS = ['.ts', '.html', '.scss', '.css'];
+// Compiled once rather than per visited file: the walk below can run over every file in the
+// project, and these patterns never change between files.
+const TABLE_TYPE_PATTERN = new RegExp(migrations_tableCellContent_data.TABLE_TYPE);
+const compiledWarnPatterns = migrations_tableCellContent_data.warnPatterns.map(({ anchor, pattern, message }) => ({
+    anchor: new RegExp(anchor),
+    pattern: new RegExp(pattern),
+    message
+}));
+/** A file is a table consumer if it imports the package, names the component, or renders one. */
+function referencesTable(content) {
+    return content.includes(migrations_tableCellContent_data.TABLE_PACKAGE) || TABLE_TYPE_PATTERN.test(content);
+}
+/**
+ * Reports the removal of `KbqTableCellContent` and the style-surface changes the table review made.
+ * Never writes: an entry in an `imports` array is deleted rather than replaced, and a stylesheet keyed
+ * on the removed modifier class has to be re-pointed at the cell.
+ *
+ * Stylesheets are visited as well as `.ts` and `.html`, because the modifier class only ever appears in
+ * CSS.
+ */
+function tableCellContent(options) {
+    return async (tree, context) => {
+        const { project } = options;
+        const projectDefinition = await utils_packageConfig.setupOptions(project, tree);
+        const root = projectDefinition?.root ?? '';
+        const rootDir = root ? tree.getDir(root) : tree.root;
+        let consumers = 0;
+        let reported = 0;
+        utils_packageConfig.visitProjectFiles(rootDir, (filePath, entry) => {
+            if (!EXTENSIONS.some((extension) => filePath.endsWith(extension)))
+                return;
+            const content = entry?.content.toString();
+            if (!content || !referencesTable(content))
+                return;
+            consumers++;
+            for (const { anchor, pattern, message } of compiledWarnPatterns) {
+                if (!anchor.test(content) || !pattern.test(content))
+                    continue;
+                reported++;
+                utils_messages.logMessage(context.logger, [`${LABEL} ${filePath}`, `  ${message}`]);
+            }
+        });
+        // Nothing here renders a table, so the summary would only be noise.
+        if (consumers === 0)
+            return;
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed kbq-table under "${root || '<workspace root>'}", ` +
+                `${consumers} file(s) reference the component, ${reported} call site(s) reported.`,
+            ...migrations_tableCellContent_data.SUMMARY
+        ]);
+    };
+}
+
+exports.default = tableCellContent;

package/schematics/migrations/table-cell-content/schema.json

@@ -0,0 +1,15 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-table-cell-content",
+    "title": "Koobiq components table review migration",
+    "type": "object",
+    "properties": {
+        "project": {
+            "type": "string",
+            "description": "Name of the project to inspect. If omitted, the migration runs over the whole tree.",
+            "$default": {
+                "$source": "projectName"
+            }
+        }
+    }
+}