@koobiq/components 20.4.2 → 21.0.1

package/schematics/migrations/notification-center-signals/README.md

@@ -0,0 +1,67 @@
+# notification-center-signals
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21`
+(registered for `21.0.0-0`). Reports the notification-center API changes a consumer's code can point
+at. It only reports — it never writes to the tree.
+
+## Background
+
+The notification-center review reworked the trigger and the service. Four of those changes break
+consumer code, and none of them can be rewritten mechanically: each needs a decision the schematic
+cannot make.
+
+## What it reports
+
+| Pattern                                                                      | Why                                                                                                                                                                                                          |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `KBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY_FACTORY_PROVIDER`                   | Gone from the entry point, so the import fails with `TS2305`. `KBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY` and `kbqNotificationCenterScrollStrategyFactory` are still exported — write the provider out by hand |
+| `onReload.emit()` / `onNextPage.emit()` / `onDelete.emit(…)`                 | The three streams are `Subject`s instead of `EventEmitter`s, so `.emit()` is gone. The replacement is `.next()`, but the member names are too common for a blind textual rewrite                             |
+| `trigger.backdropClass` / `panelClass` / `offset` / `scrolledToBottomOffset` | They are `input()` signals now: a read is a call, and a write has to become a template binding, because an `input()` has no `.set()`                                                                         |
+| `service.changes.subscribe((state) => …)`                                    | `changes` is an `Observable<void>` — a ping. The value handed to a subscriber is always `undefined`                                                                                                          |
+
+Only `.ts` files that name the notification center are looked at, so the member names above stay
+scoped to it. The last two are matched textually within such a file, so verify the reported accesses
+belong to the notification center.
+
+A read that is already written as a call (`trigger.offset()`) and a `changes` subscriber that already
+ignores its payload (`changes.subscribe(() => …)`) are not reported, so a migrated project stays
+quiet.
+
+## What it does _not_ report
+
+The `header` / `footer` fields of the trigger (never rendered) and `KbqNotificationItem` no longer
+extending `Omit<KbqToastData, 'closeButton'>` (the interface reproduces every member it used to
+inherit) are removals nothing could depend on. `KbqNotificationCenterAnimations`, which the panel never
+used, is reported by the [`angular-animations-removal`](../angular-animations-removal/README.md)
+migration.
+
+`KbqReadStateDirective`, which the notification item hosts, is covered by its own
+[`read-state-dwell-handlers`](../read-state-dwell-handlers/README.md) migration.
+
+[Params](schema.ts)
+
+Usage for Angular Cli:
+
+```shell
+ng g @koobiq/components:notification-center-signals --project "<your project>"
+```
+
+Usage for Nx:
+
+```shell
+nx g @koobiq/components:notification-center-signals --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:notification-center-signals --project koobiq-docs
+```

package/schematics/migrations/notification-center-signals/data.cjs

@@ -0,0 +1,66 @@
+'use strict';
+
+/**
+ * Data for the `notification-center-signals` migration.
+ *
+ * The notification-center review changed four things a consumer's code can point at, none of which can
+ * be rewritten mechanically — every one of them needs a decision the schematic cannot make:
+ *
+ * - `KBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY_FACTORY_PROVIDER` is gone from the entry point. The token
+ *   and its factory are still exported, so the provider has to be written out by hand.
+ * - `onReload` / `onNextPage` / `onDelete` are `Subject`s instead of `EventEmitter`s, so `.emit()` is
+ *   gone. The replacement is `.next()`, but the same member names are common enough elsewhere that a
+ *   blind textual rewrite would reach past the notification center.
+ * - `backdropClass` / `panelClass` / `offset` / `scrolledToBottomOffset` are `input()` signals: a read
+ *   is a call now, and a write has to become a template binding because an `input()` has no `.set()`.
+ * - `KbqNotificationCenterService.changes` carries no payload any more.
+ */
+/** Whether a file is worth looking at at all. */
+const NOTIFICATION_CENTER_REFERENCE = '(?:\\bKbqNotificationCenter|\\bKBQ_NOTIFICATION_CENTER_|@koobiq/components/notification-center)';
+/**
+ * File-scoped patterns, surfaced with file locations. Only evaluated for files that reference the
+ * notification center, so the member names below stay scoped to it.
+ */
+const warnPatterns = [
+    {
+        pattern: '\\bKBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY_FACTORY_PROVIDER\\b',
+        message: 'KBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY_FACTORY_PROVIDER is no longer exported from ' +
+            '@koobiq/components/notification-center, so importing it fails with TS2305. The token and its factory ' +
+            'are still exported — provide it yourself: `{ provide: KBQ_NOTIFICATION_CENTER_SCROLL_STRATEGY, ' +
+            'deps: [Overlay], useFactory: kbqNotificationCenterScrollStrategyFactory }`. The default scroll ' +
+            'strategy is already provided in root, so a provider that only reproduced it can be dropped.'
+    },
+    {
+        pattern: '\\bon(?:Reload|NextPage|Delete)\\s*\\.\\s*emit\\s*\\(',
+        message: 'KbqNotificationCenterService.onReload / onNextPage / onDelete are Subjects instead of EventEmitters, ' +
+            'so `.emit(…)` no longer exists — call `.next(…)` instead. `.subscribe(…)` is unchanged.'
+    },
+    {
+        pattern: '\\.\\s*(?:backdropClass|panelClass|offset|scrolledToBottomOffset)\\b(?!\\s*\\()',
+        requires: '\\bKbqNotificationCenterTrigger\\b',
+        message: 'backdropClass / panelClass / offset / scrolledToBottomOffset on KbqNotificationCenterTrigger are ' +
+            'input() signals now: read them as `trigger.offset()`, and replace a programmatic write with the ' +
+            'matching template binding — an input() has no `.set()`. Verify the accesses reported here belong to ' +
+            'the trigger; the names are matched textually.'
+    },
+    {
+        pattern: '\\.\\s*changes\\s*\\.\\s*subscribe\\s*\\(\\s*(?!\\(\\s*\\))',
+        requires: '\\bKbqNotificationCenterService\\b',
+        message: 'KbqNotificationCenterService.changes is an Observable<void> now — it is a ping, and the value handed ' +
+            'to a subscriber is always undefined. Read the state you need from the service itself (items, ' +
+            'silentMode, loadingMode, errorMode, loadingMore, loadMoreErrorMode, hasMore).'
+    },
+    {
+        pattern: '\\bKbqNotificationCenterModule\\b|@koobiq/components/notification-center',
+        message: 'DateAdapter and DateFormatter have to reach the ROOT injector now. KbqNotificationCenterModule used ' +
+            'to list KbqNotificationCenterService in its own providers, so the service was built in whichever ' +
+            'injector imported the module and picked up a date adapter provided there. The module no longer ' +
+            'provides it — the `providedIn: "root"` instance is the only one — so an adapter provided on a ' +
+            'feature module or a component no longer reaches it, and the first injection of the service throws ' +
+            'NG0201 "No provider found for DateAdapter". Provide the adapter at bootstrap: ' +
+            'importProvidersFrom(KbqLuxonDateModule, KbqFormattersModule), or the Moment equivalent.'
+    }
+];
+
+exports.NOTIFICATION_CENTER_REFERENCE = NOTIFICATION_CENTER_REFERENCE;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/notification-center-signals/index.cjs

@@ -0,0 +1,62 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_messages = require('../../utils/messages.cjs');
+var utils_packageConfig = require('../../utils/package-config.cjs');
+var utils_projectFiles = require('../../utils/project-files.cjs');
+var migrations_notificationCenterSignals_data = require('./data.cjs');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const TS_EXT = '.ts';
+const LABEL = '[notification-center-signals]';
+/** Hand-written TypeScript: neither a declaration file nor a template type-check file. */
+const isMigratableTs = (filePath) => filePath.endsWith(TS_EXT) && !filePath.endsWith('.d.ts') && !filePath.endsWith('.ngtypecheck.ts');
+/** Whether a `.ts` file names the notification center at all, so the member patterns stay scoped. */
+function referencesNotificationCenter(content) {
+    return new RegExp(migrations_notificationCenterSignals_data.NOTIFICATION_CENTER_REFERENCE).test(content);
+}
+function reportFile(context, filePath, content) {
+    let reported = false;
+    for (const { pattern, requires, message } of migrations_notificationCenterSignals_data.warnPatterns) {
+        if (requires && !new RegExp(requires).test(content))
+            continue;
+        if (!new RegExp(pattern).test(content))
+            continue;
+        reported = true;
+        utils_messages.logMessage(context.logger, [`${LABEL} ${filePath}`, `  ${message}`]);
+    }
+    return reported;
+}
+/**
+ * Reports the notification-center API changes a consumer's code can point at. Nothing here can be
+ * rewritten safely — every one of them needs a decision the schematic cannot make — so the migration
+ * only reports, and takes no `fix` option.
+ */
+function notificationCenterSignals(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 reported = 0;
+        utils_projectFiles.visitProjectFiles(rootDir, (filePath, entry) => {
+            // A declaration file re-states the API this reports on, so scanning one turns the report
+            // into noise about the consumer's own typings rather than their call sites.
+            if (!isMigratableTs(filePath))
+                return;
+            const content = entry?.content.toString();
+            if (!content || !referencesNotificationCenter(content))
+                return;
+            if (reportFile(context, filePath, content))
+                reported++;
+        });
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed tree under "${root || '<workspace root>'}", reported ${reported} file(s). ` +
+                'This migration reports only — every change it names needs a manual decision.'
+        ]);
+    };
+}
+
+exports.default = notificationCenterSignals;

package/schematics/migrations/notification-center-signals/schema.json

@@ -0,0 +1,15 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-notification-center-signals",
+    "title": "Koobiq components notification-center API report",
+    "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"
+            }
+        }
+    }
+}

package/schematics/migrations/option-signals/README.md

@@ -0,0 +1,37 @@
+# option-signals
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21` (registered for `21.0.0-0`).
+Migrates consumers of the signal inputs of `KbqOption`, `KbqOptgroup`, `KbqOptionActionComponent` and
+`KbqTimezoneOption`.
+
+## Background
+
+The options keep their state in signal inputs. The state consumers read through events and models stays a property
+read — `event.option.value`, `select.selected.disabled`, `option.viewValue` in a `kbqSelectTagContent` template — so
+those reads are unchanged:
+
+| Member                                                        | Read           | Programmatic write |
+| ------------------------------------------------------------- | -------------- | ------------------ |
+| `KbqOption.value`, `.viewValue`, `.disabled`, `.showCheckbox` | unchanged      | removed            |
+| `KbqTimezoneOption.timezone`                                  | unchanged      | removed            |
+| `KbqOptgroup.disabled`, `KbqOptionActionComponent.disabled`   | becomes a call | removed            |
+
+## What it rewrites
+
+A read of `disabled` on a receiver typed `KbqOptgroup` or `KbqOptionActionComponent`, or through a template reference
+on `<kbq-optgroup>` or `<kbq-option-action>`, becomes a call.
+
+## What it reports
+
+| Pattern                                              | Action                                                             |
+| ---------------------------------------------------- | ------------------------------------------------------------------ |
+| `option.value = …` and the other option state writes | Bind the input in the template.                                    |
+| `option.stateChanges`                                | No longer emits for `disabled`: read it in a `computed()` instead. |
+| `option.textElement`                                 | Typed `ElementRef \| undefined` now.                               |
+| `KbqOptionBase`                                      | `value` is an abstract getter, `disabled` has no abstract setter.  |
+
+## Running it by hand
+
+```bash
+ng g @koobiq/components:option-signals --project "<your project>"
+```

package/schematics/migrations/option-signals/data.cjs

@@ -0,0 +1,86 @@
+'use strict';
+
+/**
+ * Data for the `option-signals` migration.
+ *
+ * `KbqOption` and `KbqTimezoneOption` moved to signal inputs, but the state consumers read through events and
+ * models — `value`, `viewValue`, `disabled`, `showCheckbox`, `timezone` — is still read as a property, so only a
+ * programmatic write breaks, and it is reported. `KbqOptgroup.disabled` and `KbqOptionActionComponent.disabled`
+ * are plain signal inputs: a read becomes a call.
+ */
+const OPTION_ANCHOR = '\\bKbq(?:Option|Optgroup|TimezoneOption|VirtualOption)\\w*\\b|\\bkbq-(?:option|optgroup)\\b';
+const MEMBERS_BY_TYPE = {
+    KbqOptgroup: ['disabled'],
+    KbqOptionActionComponent: ['disabled']
+};
+const EXPORT_AS_TO_TYPE = {
+    kbqOptgroup: 'KbqOptgroup',
+    kbqOptionAction: 'KbqOptionActionComponent'
+};
+const ELEMENT_TO_TYPE = {
+    'kbq-optgroup': 'KbqOptgroup',
+    'kbq-option-action': 'KbqOptionActionComponent'
+};
+/** None: both are read-only `input()`s. */
+const WRITABLE_MEMBERS = new Set();
+const warnPatterns = [
+    {
+        anchor: OPTION_ANCHOR,
+        pattern: '\\.\\s*(?:value|viewValue|disabled|showCheckbox|timezone)\\s*=[^=]',
+        message: 'KbqOption.value, .viewValue, .disabled and .showCheckbox, and KbqTimezoneOption.timezone, are signal ' +
+            'inputs read through a getter now, so a programmatic write no longer compiles. Bind them in the ' +
+            'template instead. This pattern also matches a write to an unrelated object in a file that names an ' +
+            'option — check before changing it.'
+    },
+    {
+        anchor: OPTION_ANCHOR,
+        pattern: '\\.\\s*stateChanges\\b',
+        message: 'KbqOption.stateChanges no longer emits when the option is disabled: disabled is signal-backed, so read ' +
+            'it in a template, computed() or effect() instead.'
+    },
+    {
+        anchor: OPTION_ANCHOR,
+        pattern: '\\.\\s*textElement\\b',
+        message: 'KbqOption.textElement is a getter over a signal query now, typed ElementRef | undefined.'
+    },
+    {
+        anchor: OPTION_ANCHOR,
+        pattern: '\\bKbqOptionBase\\b',
+        message: 'KbqOptionBase.value is an abstract getter now, and KbqOptionBase no longer declares a disabled setter. ' +
+            'A subclass implements value as a getter or a property.'
+    }
+];
+const UNPARSEABLE_TEMPLATE_MESSAGE = 'This template renders an option group or an option action but could not be parsed, so it was left ' +
+    'untouched. Migrate reads of disabled through its template reference variables by hand.';
+const UNRESOLVED_RECEIVER_MESSAGE = 'An option group or an option action is used here in a way this migration cannot resolve to a single ' +
+    'receiver, so a read of disabled through it was left untouched. Check these lines by hand:';
+const SUMMARY = [
+    '  KbqOptgroup.disabled and KbqOptionActionComponent.disabled are signal inputs: a read is a call.',
+    '  The state of KbqOption is still read as a property — option.value, option.disabled — so events, models ' +
+        'and kbqSelectTagContent templates are unchanged. Only programmatic writes are gone: bind [value], ' +
+        '[disabled], [viewValue] and [showCheckbox] instead.'
+];
+const config = {
+    label: '[option-signals]',
+    package: '@koobiq/components/core',
+    membersByType: MEMBERS_BY_TYPE,
+    exportAsToType: EXPORT_AS_TO_TYPE,
+    elementToType: ELEMENT_TO_TYPE,
+    writableMembers: WRITABLE_MEMBERS,
+    warnPatterns,
+    messages: {
+        unparseableTemplate: UNPARSEABLE_TEMPLATE_MESSAGE,
+        unresolvedReceiver: UNRESOLVED_RECEIVER_MESSAGE,
+        summary: SUMMARY
+    }
+};
+
+exports.ELEMENT_TO_TYPE = ELEMENT_TO_TYPE;
+exports.EXPORT_AS_TO_TYPE = EXPORT_AS_TO_TYPE;
+exports.MEMBERS_BY_TYPE = MEMBERS_BY_TYPE;
+exports.SUMMARY = SUMMARY;
+exports.UNPARSEABLE_TEMPLATE_MESSAGE = UNPARSEABLE_TEMPLATE_MESSAGE;
+exports.UNRESOLVED_RECEIVER_MESSAGE = UNRESOLVED_RECEIVER_MESSAGE;
+exports.WRITABLE_MEMBERS = WRITABLE_MEMBERS;
+exports.config = config;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/option-signals/index.cjs

@@ -0,0 +1,20 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_signalMembersMigration = require('../../utils/signal-members-migration.cjs');
+var migrations_optionSignals_data = require('./data.cjs');
+require('typescript');
+require('../../utils/ast.cjs');
+require('../../utils/messages.cjs');
+require('../../utils/package-config.cjs');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+require('../../utils/project-files.cjs');
+require('../../utils/typescript.cjs');
+
+function optionSignals(options) {
+    return utils_signalMembersMigration.signalMembersRule(migrations_optionSignals_data.config, options);
+}
+
+exports.default = optionSignals;

package/schematics/migrations/option-signals/schema.json

@@ -0,0 +1,20 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-option-signals",
+    "title": "Koobiq components option signals migration",
+    "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/popover-leave-delay/README.md

@@ -0,0 +1,51 @@
+# popover-leave-delay
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21`
+(registered for `21.0.0-0`). Reports the popover call sites whose meaning changed in the popover
+review. It never writes to the tree.
+
+## Background
+
+Hover mode was broken end to end by a dead expression. `this.leaveDelay ?? 500` looks like a
+default, but the base class sets the field to `0`, and `0 ?? 500` is `0` — so the panel closed
+before the pointer could cross the 8px gap to it, the documented interactive content was unreachable
+even for pointer users, and the auto-hide watchdog spun as an `interval(0)` for as long as the panel
+stayed open.
+
+The delay is now derived from the trigger, and `kbqLeaveDelay` is a write-only input that records
+having been bound:
+
+- bound in the template — the bound value stands;
+- not bound — the `trigger` setter re-derives the delay on every change, so a popover switched to
+  `hover` later gets the hover default instead of the `0` it was born with.
+
+A programmatic `trigger.leaveDelay = 500` records nothing, so the next write to `trigger` overwrites
+it. That is the one change here with no compile error behind it.
+
+## What it does _not_ do
+
+Nothing is rewritten. Whether an assignment should become a `[kbqLeaveDelay]` binding or simply go
+away — the hover default is now long enough on its own — depends on why it was written.
+
+| Pattern           | Manual migration                                              |
+| ----------------- | ------------------------------------------------------------- |
+| `.leaveDelay = …` | Bind `[kbqLeaveDelay]`, or drop it and take the hover default |
+| `.onConfirm = …`  | `onConfirm` is readonly; subscribe instead of replacing       |
+| `placementChange` | The handler takes `KbqPopUpPlacementValues`, not `string`     |
+
+## Notes with no call site to point at
+
+- The confirm popover no longer hardcodes its Russian defaults. «Вы уверены, что хотите
+  продолжить?» / «Да» come from the locale now, so a non-RU application renders translated text
+  where it used to render Russian.
+- The trigger subscribed to the global `ScrollDispatcher` with no teardown in the _default_
+  configuration. That subscription is bounded now, so a host that worked around the leak by
+  destroying triggers eagerly can stop.
+- `KbqPopoverTrigger` can be imported standalone — the scroll-strategy provider is no longer
+  NgModule-only.
+
+## Running it manually
+
+```
+ng generate @koobiq/components:popover-leave-delay --project my-app
+```

package/schematics/migrations/popover-leave-delay/data.cjs

@@ -0,0 +1,61 @@
+'use strict';
+
+/**
+ * Data for the `popover-leave-delay` migration.
+ *
+ * The popover review fixed a dead `this.leaveDelay ?? 500` — the base sets the field to `0`,
+ * so `0 ?? 500` is `0` and hover mode closed the panel before the pointer could cross the 8px gap to
+ * it. The delay is now derived from the trigger, and `kbqLeaveDelay` became a write-only input that
+ * records having been bound:
+ *
+ * - bound in the template → the bound value stands;
+ * - not bound → the `trigger` setter re-derives the delay on every change, so a popover switched to
+ *   `hover` later gets the hover default instead of the `0` it was born with.
+ *
+ * A programmatic `trigger.leaveDelay = 500` does not record anything, so the next write to `trigger`
+ * overwrites it. That is the one change here with no compile error behind it.
+ *
+ * Warn-only. Whether a call site should move to the `kbqLeaveDelay` binding or drop its assignment
+ * (the hover default is now correct on its own) depends on why it was written.
+ */
+/** Import specifier that marks a file as a popover consumer. */
+const POPOVER_PACKAGE = '@koobiq/components/popover';
+/** Identifier and attribute shapes that mark a consumer without an import. */
+const POPOVER_TYPE = '\\bKbqPopover\\w*\\b|\\bkbqPopover\\b';
+const warnPatterns = [
+    {
+        anchor: POPOVER_TYPE,
+        pattern: '\\.\\s*leaveDelay\\s*=(?!=)',
+        message: 'Assigning KbqPopoverTrigger.leaveDelay no longer sticks. The delay is re-derived from `trigger` ' +
+            'on every change unless the `kbqLeaveDelay` input was bound, and a programmatic write does not ' +
+            'record that — the next write to `trigger` overwrites it. Bind [kbqLeaveDelay] instead, or drop ' +
+            'the assignment: hover mode now defaults to a delay long enough to reach the panel, which the ' +
+            'dead `?? 500` never produced.'
+    },
+    {
+        anchor: POPOVER_TYPE,
+        pattern: '\\.\\s*onConfirm\\s*=(?!=)',
+        message: 'KbqPopoverConfirmComponent.onConfirm is readonly. Subscribe to it instead of replacing it.'
+    },
+    {
+        anchor: POPOVER_TYPE,
+        pattern: '\\bplacementChange\\b',
+        message: 'kbqPopoverPlacementChange emits string instead of any. A handler declared `(p: string)` is ' +
+            'unaffected; only code that assigned the payload to something other than a string stops compiling.'
+    }
+];
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  The confirm popover no longer hardcodes its Russian defaults: «Вы уверены, что хотите ' +
+        'продолжить?» / «Да» now come from the locale, so a non-RU application renders translated text ' +
+        'where it used to render Russian. Override them through the popover-confirm locale section.',
+    '  The trigger subscribed to the global ScrollDispatcher with no teardown in the default ' +
+        'configuration; that subscription is now bounded, so a host that worked around the leak by ' +
+        'destroying triggers eagerly can stop.',
+    '  KbqPopoverTrigger can be imported standalone — the scroll-strategy provider is no longer ' + 'NgModule-only.'
+];
+
+exports.POPOVER_PACKAGE = POPOVER_PACKAGE;
+exports.POPOVER_TYPE = POPOVER_TYPE;
+exports.SUMMARY = SUMMARY;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/popover-leave-delay/index.cjs

@@ -0,0 +1,55 @@
+'use strict';
+
+Object.defineProperty(exports, '__esModule', { value: true });
+
+var utils_messages = require('../../utils/messages.cjs');
+var utils_packageConfig = require('../../utils/package-config.cjs');
+var utils_projectFiles = require('../../utils/project-files.cjs');
+var migrations_popoverLeaveDelay_data = require('./data.cjs');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const LABEL = '[popover-leave-delay]';
+const EXTENSIONS = ['.ts', '.html'];
+/** A file is a popover consumer if it imports the package, names a popover type, or renders one. */
+function referencesPopover(content) {
+    return content.includes(migrations_popoverLeaveDelay_data.POPOVER_PACKAGE) || new RegExp(migrations_popoverLeaveDelay_data.POPOVER_TYPE).test(content);
+}
+/**
+ * Reports the popover call sites the review changed the meaning of. Never writes: whether an
+ * assignment should become a `kbqLeaveDelay` binding or simply go away depends on why it was made.
+ */
+function popoverLeaveDelay(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_projectFiles.visitProjectFiles(rootDir, (filePath, entry) => {
+            if (!EXTENSIONS.some((extension) => filePath.endsWith(extension)))
+                return;
+            const content = entry?.content.toString();
+            if (!content || !referencesPopover(content))
+                return;
+            consumers++;
+            for (const { anchor, pattern, message } of migrations_popoverLeaveDelay_data.warnPatterns) {
+                if (!new RegExp(anchor).test(content) || !new RegExp(pattern).test(content))
+                    continue;
+                reported++;
+                utils_messages.logMessage(context.logger, [`${LABEL} ${filePath}`, `  ${message}`]);
+            }
+        });
+        // Nothing here renders a popover, so the summary would only be noise.
+        if (consumers === 0)
+            return;
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed kbqPopover under "${root || '<workspace root>'}", ` +
+                `${consumers} file(s) reference the popover, ${reported} call site(s) reported.`,
+            ...migrations_popoverLeaveDelay_data.SUMMARY
+        ]);
+    };
+}
+
+exports.default = popoverLeaveDelay;

package/schematics/migrations/popover-leave-delay/schema.json

@@ -0,0 +1,15 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-popover-leave-delay",
+    "title": "Koobiq components popover 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"
+            }
+        }
+    }
+}

package/schematics/migrations/progress-bar-percentage-and-aria/README.md

@@ -0,0 +1,54 @@
+# progress-bar-percentage-and-aria
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21` (registered for
+`21.0.0-0`). Reports the progress-bar review changes a consumer has to act on. It never writes to
+the tree.
+
+## Background
+
+The review closed the one member that only ever existed to feed the template, and gave the bar the
+progress semantics it had none of.
+
+| Member / markup                                                  | Before          | After                                           |
+| ---------------------------------------------------------------- | --------------- | ----------------------------------------------- |
+| `percentage`                                                     | public getter   | `protected` computed                            |
+| `aria-label` on `<kbq-progress-bar>`                             | plain attribute | input, aliased `aria-label`                     |
+| `role`, `aria-valuenow`, `aria-valuemin`, `aria-valuemax`        | absent          | rendered by the host                            |
+| `id` on `[kbq-progress-bar-text]` / `[kbq-progress-bar-caption]` | absent          | rendered, generated when not bound              |
+| `id` on the inner track                                          | host's own `id` | removed — one element per bar carries that `id` |
+
+`percentage` deserves a note. It was a getter over the clamped `value`, re-evaluated on every change
+detection pass, and the only thing that read it was the component's own template. The clamp is still
+observable: it is the width of the fill, and it is `aria-valuenow` on the host.
+
+## What it does _not_ do
+
+Nothing is rewritten. `percentage` has no drop-in replacement expression, and which of two competing
+`aria-*` attributes survives on a host element is a decision the call site owns.
+
+| Pattern                                               | Manual migration                                             |
+| ----------------------------------------------------- | ------------------------------------------------------------ |
+| `.percentage`                                         | Clamp at the call site, or read `aria-valuenow` off the host |
+| `role` / `aria-value*` / `aria-labelledby` on the bar | Drop it — the component renders its own                      |
+| `[attr.aria-label]` on the bar                        | Bind `[aria-label]`; the host writes that attribute itself   |
+
+## Notes with no call site to point at
+
+- Under `prefers-reduced-motion: reduce` an indeterminate bar used to render as a full, finished
+  determinate bar: the fill was sized only inside the keyframes, so `animation: none` left it at
+  `width: auto` over a track it completely covered. It is a quarter-width fill with an opacity pulse
+  now, and the determinate `width` transition is suppressed under the same preference.
+- The indeterminate animation interpolates `transform` only. It used to animate `width` as well,
+  which forced layout on every frame of an infinite loop and made the `translateX()` percentages
+  resolve against a width that was itself changing.
+- `[color]` covers `theme` (the default), `contrast`, `contrast-fade` and `error`. Every other value
+  used to leave both the track and the fill transparent, because the theme mixin was scoped to
+  `.kbq-theme` alone; an unsupported — or falsy — value falls back to the default palette now.
+- The a11y locale gained a `progressBar` key, used as the accessible name of a bar that carries
+  neither an `aria-label` nor a projected `[kbq-progress-bar-text]`.
+
+## Running it manually
+
+```
+ng generate @koobiq/components:progress-bar-percentage-and-aria --project my-app
+```