@koobiq/components 20.4.2 → 21.0.0

package/schematics/migrations/clamped-text-disclosure/README.md

@@ -0,0 +1,62 @@
+# clamped-text-disclosure
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21`
+(registered for `21.0.0-0`). Reports the call sites the clamped-text review breaks. It never writes
+to the tree.
+
+## Background
+
+The review moved the disclosure semantics onto the control that is actually operated, and returned
+the trigger's styling to its owner:
+
+| What                                                  | Before                                                | After                                     |
+| ----------------------------------------------------- | ----------------------------------------------------- | ----------------------------------------- |
+| `aria-expanded`                                       | on the `<kbq-clamped-text>` / `[kbqClampedList]` host | on the `[kbqClampedListTrigger]` element  |
+| `role`, `tabindex`, `aria-controls`                   | nowhere, or hand-written per call site                | supplied by `KbqClampedListTrigger`       |
+| `kbq-clamped-text__toggle` on the trigger             | applied to every trigger                              | applied only by the clamped-text template |
+| `KbqClampedText.isCollapsed`                          | `input()` + `output()` pair                           | `model()`                                 |
+| `isCollapsedChange`                                   | fired on measurement and echoed parent writes         | user intent only                          |
+| `KbqClampedText.hasToggle`                            | `WritableSignal<boolean>`                             | `Signal<boolean>`                         |
+| `KbqClampedText.text`, `KbqClampedText.textContainer` | public view queries                                   | `protected`                               |
+
+Both containers are role-less wrappers, so `aria-expanded` on them conveyed nothing to assistive
+technology and sat on an element the user cannot operate. The trigger — the element that takes the
+click and the Enter/Space keys — carried no semantics at all, which is why the library's own
+examples disagreed with each other about what to write on it.
+
+`kbq-clamped-text__toggle` has one rule, in the clamped-text stylesheet, injected only once a
+`KbqClampedText` exists. A `kbqClampedList` trigger therefore had spacing or not depending on
+whether an unrelated component happened to be on the page, and both in-repo examples cancelled it
+independently.
+
+## What it does _not_ do
+
+Nothing is rewritten. Where `aria-expanded` should be read from, what replaces a cancelled margin
+and whether an `isCollapsedChange` handler wanted the mount-time value are all decisions.
+
+| Pattern                                     | Manual migration                                                       |
+| ------------------------------------------- | ---------------------------------------------------------------------- |
+| `aria-expanded` on the container            | Read it off the `[kbqClampedListTrigger]` element                      |
+| `.kbq-clamped-text__toggle` override        | Drop it; the list trigger has no spacing of its own now                |
+| `role="button"` on the trigger              | Remove it — the directive supplies it, and an explicit role still wins |
+| `(isCollapsedChange)` for the initial state | Read the state from `[(isCollapsed)]`; the output is user intent only  |
+| `.hasToggle.set(…)`                         | Read-only; it is written by the measurement                            |
+| `.text()` / `.textContainer()`              | Protected; query the element from your own template                    |
+
+## Notes with no call site to point at
+
+- Collapsing scrolls with `{ block: 'nearest', inline: 'nearest' }` instead of centering on both
+  axes, so it no longer pans an ancestor horizontally. `[scrollOnCollapse]="false"` turns it off.
+- Space and Enter on the trigger call `preventDefault()`. Space no longer scrolls the page while
+  expanding, and a native `<button>` host no longer toggles twice from the synthetic click.
+- `rows` takes a string attribute now, so `rows="3"` compiles under `strictTemplates`.
+- `[debounceTime]` is re-read on every resize instead of once in `ngAfterViewInit`.
+- Nothing renders before the first measurement: the toggle appears once the content is known to
+  overflow, and the text stays clamped until then rather than flashing in full — including in
+  server-rendered and prerendered output.
+
+## Running it manually
+
+```
+ng generate @koobiq/components:clamped-text-disclosure --project my-app
+```

package/schematics/migrations/clamped-text-disclosure/data.js

@@ -0,0 +1,101 @@
+'use strict';
+
+/**
+ * Data for the `clamped-text-disclosure` migration.
+ *
+ * The clamped-text review moved the disclosure semantics onto the control that is actually
+ * operated and tightened the surface around the measurement:
+ *
+ * - `aria-expanded` is no longer rendered on the `<kbq-clamped-text>` host or on the
+ *   `[kbqClampedList]` container. Both are role-less wrappers; `KbqClampedListTrigger` publishes
+ *   `role`, `tabindex`, `aria-expanded` and `aria-controls` on itself now.
+ * - `KbqClampedListTrigger` no longer puts `kbq-clamped-text__toggle` on its host, so a
+ *   `kbqClampedList` trigger no longer inherits the clamped-text margin — which only applied when
+ *   an unrelated `kbq-clamped-text` happened to be on the page.
+ * - `KbqClampedText.isCollapsed` is a `model()`. `isCollapsedChange` reports user intent only: it
+ *   no longer fires for the component's first measurement nor echoes a value the parent wrote.
+ * - `KbqClampedText.hasToggle` is read-only, and `text` / `textContainer` are `protected`.
+ * - Collapsing scrolls with `{ block: 'nearest', inline: 'nearest' }` and can be turned off with
+ *   `[scrollOnCollapse]="false"`.
+ *
+ * Warn-only. Where `aria-expanded` has to be read from, what replaces a removed class and whether
+ * an `isCollapsedChange` handler wanted the initial value are all decisions an automatic rewrite cannot make.
+ */
+/** Import specifier that marks a file as a clamped-text consumer. */
+const CLAMPED_TEXT_PACKAGE = '@koobiq/components/clamped-text';
+/** Identifier, element, attribute and class shapes that mark a consumer without an import. */
+const CLAMPED_TEXT_TYPE = '\\bKbqClamped\\w*\\b|\\bkbq-clamped-\\w+|\\bkbqClampedList\\w*\\b';
+/** Files that render one of the two containers, as opposed to naming any symbol of the package. */
+const CLAMPED_CONTAINER = '\\bKbqClampedText\\b|\\bkbq-clamped-text\\b|\\bkbqClampedList\\b|\\bKbqClampedList\\b';
+/** Files that place the trigger themselves. */
+const CLAMPED_TRIGGER = '\\bkbqClampedListTrigger\\b|\\bKbqClampedListTrigger\\b';
+/** Files that render the clamped text, whose two-way channel changed semantics. */
+const CLAMPED_TEXT_ONLY = '\\bKbqClampedText\\b|\\bkbq-clamped-text\\b';
+const warnPatterns = [
+    {
+        anchor: CLAMPED_CONTAINER,
+        pattern: '\\baria-expanded\\b',
+        message: 'aria-expanded is no longer rendered on the <kbq-clamped-text> host or on the [kbqClampedList] ' +
+            'container — both are role-less wrappers, where the attribute conveyed nothing. The trigger ' +
+            'publishes it now, together with role="button", tabindex and aria-controls. A selector or ' +
+            'assertion that reads the state off the container has to read it off the ' +
+            '[kbqClampedListTrigger] element instead.'
+    },
+    {
+        anchor: CLAMPED_TEXT_TYPE,
+        pattern: '\\bkbq-clamped-text__toggle\\b',
+        message: 'KbqClampedListTrigger no longer carries the kbq-clamped-text__toggle class: the margin it ' +
+            'brought came from the clamped-text stylesheet and only applied when a kbq-clamped-text ' +
+            'happened to be rendered somewhere on the page. A kbqClampedList trigger now has no spacing ' +
+            'of its own — lay it out with the list, and drop any margin-top override written against it. ' +
+            'The clamped-text toggle keeps the class and is adjustable through ' +
+            '--kbq-clamped-text-size-toggle-margin.'
+    },
+    {
+        anchor: CLAMPED_TRIGGER,
+        pattern: '\\brole\\s*=\\s*["\'`]button["\'`]',
+        message: 'kbqClampedListTrigger supplies role="button" and tabindex="0" itself. A hand-written role on ' +
+            'the trigger element is now a duplicate; remove it unless you deliberately want a different ' +
+            'role, which still wins over the directive default.'
+    },
+    {
+        anchor: CLAMPED_TEXT_ONLY,
+        pattern: '\\bisCollapsedChange\\b',
+        message: 'KbqClampedText.isCollapsed is a model() and isCollapsedChange reports user intent only: it no ' +
+            "longer fires for the component's own first measurement, and no longer echoes a value the " +
+            'parent wrote into [isCollapsed]. A handler that relied on the mount-time emission to learn ' +
+            'the initial state has to read it from [(isCollapsed)] instead.'
+    },
+    {
+        anchor: CLAMPED_TEXT_ONLY,
+        pattern: '\\.\\s*hasToggle\\s*\\.\\s*(?:set|update)\\s*\\(',
+        message: 'KbqClampedText.hasToggle is a read-only Signal now, matching the KbqClamped contract. It is ' +
+            'written by the measurement; setting it from outside desynchronized the component from its ' +
+            'own layout.'
+    },
+    {
+        anchor: CLAMPED_TEXT_ONLY,
+        pattern: '\\.\\s*(?:textContainer|text)\\s*\\(\\s*\\)\\s*\\.\\s*nativeElement',
+        message: 'KbqClampedText.text and KbqClampedText.textContainer are protected: they were view queries ' +
+            "into the component's own DOM. Query the rendered element from the host template instead."
+    }
+];
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  Collapsing scrolls with { block: "nearest", inline: "nearest" } instead of centering on both ' +
+        'axes, so it no longer pans an ancestor horizontally, and [scrollOnCollapse]="false" turns it ' +
+        'off entirely.',
+    '  Space and Enter on the trigger call preventDefault(): Space no longer scrolls the page while ' +
+        'expanding, and a native <button> host no longer toggles twice from the synthetic click.',
+    '  rows takes a string attribute now (numberAttribute), so rows="3" compiles under strictTemplates ' +
+        'the way debounceTime="300" already did.',
+    '  [debounceTime] is re-read on every resize instead of once at ngAfterViewInit, so a bound value ' +
+        'that changes now applies.',
+    '  Nothing renders before the first measurement any more: the toggle appears once the content is ' +
+        'known to overflow, and the text is clamped until then rather than flashing in full.'
+];
+
+exports.CLAMPED_TEXT_PACKAGE = CLAMPED_TEXT_PACKAGE;
+exports.CLAMPED_TEXT_TYPE = CLAMPED_TEXT_TYPE;
+exports.SUMMARY = SUMMARY;
+exports.warnPatterns = warnPatterns;

package/schematics/migrations/clamped-text-disclosure/index.js

@@ -0,0 +1,59 @@
+'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_clampedTextDisclosure_data = require('./data.js');
+require('@angular-devkit/schematics');
+require('@schematics/angular/utility');
+
+const LABEL = '[clamped-text-disclosure]';
+const EXTENSIONS = ['.ts', '.html', '.scss', '.css'];
+/** A file is a clamped-text consumer if it imports the package, names a symbol, or renders one. */
+function referencesClampedText(content) {
+    return content.includes(migrations_clampedTextDisclosure_data.CLAMPED_TEXT_PACKAGE) || new RegExp(migrations_clampedTextDisclosure_data.CLAMPED_TEXT_TYPE).test(content);
+}
+/**
+ * Reports the call sites the clamped-text review breaks: the `aria-expanded` that moved from the
+ * containers to the trigger, the borrowed toggle class the trigger stopped applying, the
+ * `isCollapsedChange` that no longer fires for the component's own measurement, and the members
+ * that became read-only or protected. Never writes: each of those is a decision, not a rename.
+ *
+ * `.scss` and `.css` are visited as well, because the borrowed class is most often overridden from
+ * a stylesheet rather than from a template.
+ */
+function clampedTextDisclosure(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 || !referencesClampedText(content))
+                return;
+            consumers++;
+            for (const { anchor, pattern, message } of migrations_clampedTextDisclosure_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 clamped text or list, so the summary would only be noise.
+        if (consumers === 0)
+            return;
+        utils_messages.logMessage(context.logger, [
+            `${LABEL} processed @koobiq/components/clamped-text under "${root || '<workspace root>'}", ` +
+                `${consumers} file(s) reference the package, ${reported} call site(s) reported.`,
+            ...migrations_clampedTextDisclosure_data.SUMMARY
+        ]);
+    };
+}
+
+exports.default = clampedTextDisclosure;

package/schematics/migrations/clamped-text-disclosure/schema.json

@@ -0,0 +1,15 @@
+{
+    "$schema": "http://json-schema.org/schema",
+    "$id": "koobiq-components-clamped-text-disclosure",
+    "title": "Koobiq components clamped-text 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/code-block-signals/README.md

@@ -0,0 +1,84 @@
+# code-block-signals
+
+Migration schematic invoked automatically by `ng update @koobiq/components@21` (registered for
+`21.0.0-0`). Moves `KbqCodeBlock` consumers onto its finished signal-based API and reports what has no
+mechanical translation.
+
+## Background
+
+`maxHeight` was published as `InputSignal<number>` over an `undefined!` default, so a code block with
+no `[maxHeight]` binding reported `undefined` from a non-nullable type:
+
+```ts
+const height: number = codeBlock.maxHeight(); // held undefined
+if (codeBlock.maxHeight() > 0) { … }          // NaN comparison, never true
+```
+
+It reports `number | undefined` now, and a value that is not cleanly numeric — a valueless
+`maxHeight` attribute, `'200px'` — reports `undefined` rather than `NaN`. `[maxHeight]="undefined"`
+used to hand back `NaN`; that is the one runtime change. The call sites that were quietly wrong now
+fail to compile.
+
+`KbqCodeBlockHighlight.file` was a write-only required input: a setter with no getter that kicked off
+highlighting as a side effect. It is `input.required()` driven by an effect now, so it can finally be
+read — and a programmatic write no longer compiles.
+
+## What it rewrites
+
+`KbqCodeBlock` has no decorator inputs left. `softWrap`, `viewAll`, `canDownload`, `files`,
+`activeFileIndex` and `hideTabs` are `WritableSignal`s over a backing `input()`, so both directions
+are mechanical:
+
+| Before                      | After                          |
+| --------------------------- | ------------------------------ |
+| `block.softWrap`            | `block.softWrap()`             |
+| `block.activeFileIndex = 2` | `block.activeFileIndex.set(2)` |
+
+On receivers explicitly typed `KbqCodeBlock`, on the `inject()` / `viewChild()` initializer forms, and
+through template reference variables on `<kbq-code-block>` in external and inline templates. Reads that
+are already calls are left alone, so the schematic is idempotent.
+
+A `model()` would have been the obvious shape for the six, but `ModelOptions` carries no `transform`,
+and every one of them needs `booleanAttribute` or `numberAttribute` to keep a valueless attribute such
+as `<kbq-code-block softWrap>` working.
+
+## What it does _not_ do
+
+Narrowing `number | undefined` back to `number` is a decision — `?? 0`, a non-null assertion, or
+handling the unset state — and turning a `file` write into a `[file]` binding is a template edit. A
+compound assignment (`||=`, `+=`) or an increment would need the receiver spelled twice, so it is
+reported rather than rewritten, and the backing inputs — `softWrapInput` and friends — cannot be
+written at all any more. The removed `canLoad` and `codeFiles` aliases are migrated by `v21-upgrade`.
+
+| Pattern                                  | Manual migration                                                    |
+| ---------------------------------------- | ------------------------------------------------------------------- |
+| `.maxHeight()` on a `KbqCodeBlock`       | `?? 0` for the common reading, or handle the unset state explicitly |
+| `.file = …` on a `KbqCodeBlockHighlight` | Bind `[file]`; the value is readable as `file()` now                |
+
+## Notes with no call site to point at
+
+- The `max-height` the code block applies while `viewAll` is off is a `computed`. It was a getter read
+  from a `[style.max-height.px]` binding, so it only re-evaluated when something else marked the view
+  dirty; it follows `maxHeight` and `viewAll` directly now.
+- `softWrap`, `viewAll`, `canDownload`, `activeFileIndex` and `files` are backed by signals. They are
+  accessor inputs with the same types and the same two-way outputs — they are written by the component
+  as well as by the binding, and a `model()` cannot carry the `booleanAttribute` /
+  `numberAttribute` transform they need. Four of the five were plain public fields before, so they are
+  no longer own properties: they do not appear in `Object.keys`, a spread or `JSON.stringify`, and a
+  subclass field of the same name shadows the accessor under `useDefineForClassFields`.
+- **`hideTabs` is derived rather than written.** A single file with no filename still hides the tab
+  bar, but the component no longer writes `true` into its own input to do it: the write latched the
+  bar off for good and re-emitted `hideTabsChange` on every `files` assignment. `[hideTabs]="false"`
+  no longer shows the bar for a lone unnamed file.
+- **An `activeFileIndex` outside `files` renders the first file, and an empty `files` renders no code
+  at all.** Both used to reach `files[activeFileIndex]` and throw on the undefined result. The index
+  itself is left as bound: resetting it wrote back into a `[(activeFileIndex)]` while the parent was
+  still updating.
+- A failed `highlight.js` load no longer latches `pending` on, and the line-numbers plugin installs
+  its `<style>` and its `copy` listener once instead of once per code block.
+
+## Running it manually
+
+```
+ng generate @koobiq/components:code-block-signals --project my-app
+```

package/schematics/migrations/code-block-signals/data.js

@@ -0,0 +1,121 @@
+'use strict';
+
+/**
+ * Data for the `code-block-signals` migration.
+ *
+ * `KbqCodeBlock` finished its move to signals: nothing on it is a decorator input any more.
+ *
+ * - `softWrap`, `viewAll`, `canDownload`, `files`, `activeFileIndex`, `hideTabs` → `WritableSignal`s over
+ *   a backing `input()`, so a read becomes a call and a plain write becomes `.set(…)` (auto-fixed)
+ * - `maxHeight` was already a signal input; only its type changed (warn)
+ *
+ * A `model()` would have been the obvious shape for the six, but `ModelOptions` carries no `transform`,
+ * and every one of them needs `booleanAttribute` or `numberAttribute` to keep a valueless attribute
+ * (`<kbq-code-block softWrap>`) working. Hence the backing input plus a `linkedSignal` over it.
+ */
+/** Members whose value is unchanged; a read must become a call, a write must become `.set(…)`. */
+const SIGNAL_MEMBERS = [
+    'softWrap',
+    'viewAll',
+    'canDownload',
+    'files',
+    'activeFileIndex',
+    'hideTabs'
+];
+/**
+ * Members the migration reports rather than rewrites: `maxHeight` was already a signal input and only
+ * changed its type, and `KbqCodeBlockHighlight.file` turned from a write-only setter into a required
+ * input. Both are reported per file, because a summary line names no call site.
+ */
+const REPORTED_MEMBERS = ['maxHeight', 'file'];
+/** Signal-API methods reachable on a signal; a read followed by one is already migrated. */
+const SIGNAL_API_METHODS = new Set(['set', 'update', 'asReadonly', 'subscribe']);
+/** `exportAs` name a template reference has to carry to be the code block rather than some other directive. */
+const CODE_BLOCK_EXPORT_AS = 'kbqCodeBlock';
+/** TypeScript type annotation that marks a receiver as a code block. */
+const CODE_BLOCK_TYPE = 'KbqCodeBlock';
+/** Type annotation that marks a receiver as the highlight directive, whose `file` input also changed. */
+const HIGHLIGHT_TYPE = 'KbqCodeBlockHighlight';
+/** Element selector whose template reference variables (`#ref`) point at a code block. */
+const CODE_BLOCK_ELEMENT = 'kbq-code-block';
+/** Import specifier that marks a file as a code block consumer. */
+const CODE_BLOCK_PACKAGE = '@koobiq/components/code-block';
+/**
+ * The backing inputs behind the six signals. Public, because a `protected` input cannot be bound from a
+ * consumer's template, but they are `@docs-private` plumbing: read the signal that carries the attribute's
+ * own name instead. The removed `canLoadInput` and `codeFilesInput` are reported by `v21-upgrade`.
+ */
+const PLUMBING_MEMBERS = [
+    'softWrapInput',
+    'viewAllInput',
+    'canDownloadInput',
+    'filesInput',
+    'activeFileIndexInput',
+    'hideTabsInput'
+];
+/** Reported for a write the rewrite cannot translate on its own. */
+const writeMessage = (members) => `These writes were left untouched: ${[...members].join(', ')}. A plain \`x.softWrap = value\` is ` +
+    'rewritten to `x.softWrap.set(value)`, but a compound assignment (`||=`, `+=`) or an increment would ' +
+    'need the receiver spelled twice.';
+const reportedMessage = (members) => `These KbqCodeBlock members changed shape without changing name: ${[...members].join(', ')}. ` +
+    '`maxHeight` reports `number | undefined` instead of `number` and never NaN, so decide per call site ' +
+    'between `?? 0` and handling the unset state. `KbqCodeBlockHighlight.file` was a write-only setter ' +
+    'and is a required input now: bind `[file]`, and read it as `file()`.';
+const plumbingMessage = (members) => `These KbqCodeBlock members are backing inputs: ${[...members].join(', ')}. They exist to carry the ` +
+    'attribute and its transform, they are read-only, and they report what was bound rather than what the ' +
+    'component currently holds. Bind the attribute they alias - `softWrap`, `viewAll`, `canDownload`, ' +
+    "`files`, `activeFileIndex`, `hideTabs` - and read the signal that carries the attribute's own name.";
+/**
+ * Reported for a read through a signal query, which is a signal holding the component: the read needs two
+ * calls rather than one. Emitted from the AST pass rather than a regex, so it follows the same receiver
+ * resolution as the rewrite.
+ */
+const signalQueryMessage = (member, required) => `A signal query holds the component behind a call of its own, so reading \`${member}\` through it ` +
+    `needs two calls: \`this.codeBlock()${required ? '' : '?'}.${member}()\`.` +
+    (required ? '' : ' The query is optional, so keep the `?.`.') +
+    ' Those reads are left untouched - migrate them by hand.';
+/** Reported when a template renders the code block but cannot be parsed, so nothing in it was inspected. */
+const UNPARSEABLE_TEMPLATE_MESSAGE = 'This template renders <kbq-code-block> but could not be parsed, so it was left untouched. Migrate ' +
+    'reads through its template reference variables by hand. If every template is reported this way, ' +
+    '`@angular/compiler` could not be loaded from this install.';
+/**
+ * Reported when a file names `KbqCodeBlock` in a type position the receiver pass cannot scope to a single
+ * identifier - a union, an array, a `QueryList<…>`, a cast, a return type - or reads a member in a shape
+ * the access pass cannot reach.
+ */
+const UNRESOLVED_RECEIVER_MESSAGE = 'KbqCodeBlock is used here in a way this migration cannot resolve to a single receiver, so any signal ' +
+    'read through it was left untouched. Check these lines by hand:';
+/** Printed once per project, after the per-file reports. */
+const SUMMARY = [
+    '  `maxHeight` reports `number | undefined` instead of `number`, and a value that is not cleanly ' +
+        "numeric - a valueless `maxHeight` attribute, `'200px'` - reports `undefined` rather than NaN. " +
+        'It was declared non-nullable over an `undefined!` default, so a block with no binding always ' +
+        'handed back `undefined` behind a `number` type.',
+    '  `KbqCodeBlockHighlight.file` was a write-only required input that started highlighting as a side ' +
+        'effect. It is a required signal input driven by an effect now, so it can finally be read - and a ' +
+        'programmatic write no longer compiles.',
+    '  Reading `hideTabs` reports what was bound. What the header actually does is `tabsHidden()`, which ' +
+        'adds the rule that a single file with no filename hides the bar; the component used to write that ' +
+        'rule into `hideTabs` itself, which latched the bar off for good.',
+    '  An `activeFileIndex` outside `files` renders the first file instead of the indexed one, and an ' +
+        'empty `files` renders no code at all. Both used to reach `files[activeFileIndex]` and throw on ' +
+        'the undefined result. The index itself is left alone: resetting it wrote back into ' +
+        '`[(activeFileIndex)]` while the parent was still updating.'
+];
+
+exports.CODE_BLOCK_ELEMENT = CODE_BLOCK_ELEMENT;
+exports.CODE_BLOCK_EXPORT_AS = CODE_BLOCK_EXPORT_AS;
+exports.CODE_BLOCK_PACKAGE = CODE_BLOCK_PACKAGE;
+exports.CODE_BLOCK_TYPE = CODE_BLOCK_TYPE;
+exports.HIGHLIGHT_TYPE = HIGHLIGHT_TYPE;
+exports.PLUMBING_MEMBERS = PLUMBING_MEMBERS;
+exports.REPORTED_MEMBERS = REPORTED_MEMBERS;
+exports.SIGNAL_API_METHODS = SIGNAL_API_METHODS;
+exports.SIGNAL_MEMBERS = SIGNAL_MEMBERS;
+exports.SUMMARY = SUMMARY;
+exports.UNPARSEABLE_TEMPLATE_MESSAGE = UNPARSEABLE_TEMPLATE_MESSAGE;
+exports.UNRESOLVED_RECEIVER_MESSAGE = UNRESOLVED_RECEIVER_MESSAGE;
+exports.plumbingMessage = plumbingMessage;
+exports.reportedMessage = reportedMessage;
+exports.signalQueryMessage = signalQueryMessage;
+exports.writeMessage = writeMessage;