@oxyhq/bloom 1.0.5 → 1.0.6

package/src/__tests__/support/constructed-style-sheets.ts

@@ -1,68 +0,0 @@
-/**
- * A spec-shaped stand-in for constructed stylesheets, for the jsdom suites.
- *
- * jsdom 26 ships the `CSSStyleSheet` CONSTRUCTOR but neither `replaceSync` nor
- * `document.adoptedStyleSheets`, so every jsdom test takes Bloom's `<style>`
- * fallback. That makes the whole CSP-safe path — the reason
- * `styles/adopt-style-sheet.ts` exists — invisible to jest unless a test
- * installs the API itself. Without this, a mutation that deleted the adoption
- * branch entirely would leave the suite green.
- *
- * Not collected as a suite: jest's `testMatch` wants `*.test.ts` / `*.spec.ts`.
- */
-
-export interface FakeStyleSheet {
-  /** The CSS most recently handed to `replaceSync`. */
-  cssText: string;
-  /** How many times the sheet has been re-parsed, so a test can prove it wasn't. */
-  replaceSyncCalls: number;
-  replaceSync(css: string): void;
-}
-
-export interface ConstructedStyleSheetsHarness {
-  /** The document's adopted sheets, read live (the code reassigns the array). */
-  adopted(): readonly FakeStyleSheet[];
-  /** Drop the API again, restoring jsdom's own `CSSStyleSheet`. */
-  uninstall(): void;
-}
-
-export function installConstructedStyleSheets(): ConstructedStyleSheetsHarness {
-  class FakeCSSStyleSheet implements FakeStyleSheet {
-    cssText = '';
-    replaceSyncCalls = 0;
-
-    replaceSync(css: string): void {
-      this.cssText = css;
-      this.replaceSyncCalls += 1;
-    }
-  }
-
-  const previousConstructor = Object.getOwnPropertyDescriptor(
-    globalThis,
-    'CSSStyleSheet',
-  );
-
-  Object.defineProperty(globalThis, 'CSSStyleSheet', {
-    value: FakeCSSStyleSheet,
-    writable: true,
-    configurable: true,
-  });
-  Object.defineProperty(document, 'adoptedStyleSheets', {
-    value: [],
-    writable: true,
-    configurable: true,
-  });
-
-  return {
-    adopted: () =>
-      document.adoptedStyleSheets as unknown as readonly FakeStyleSheet[],
-    uninstall: () => {
-      Reflect.deleteProperty(document, 'adoptedStyleSheets');
-      if (previousConstructor) {
-        Object.defineProperty(globalThis, 'CSSStyleSheet', previousConstructor);
-      } else {
-        Reflect.deleteProperty(globalThis, 'CSSStyleSheet');
-      }
-    },
-  };
-}

package/src/__tests__/support/press-host.ts

@@ -1,30 +0,0 @@
-/**
- * Pressing a component's OWN host node, and proving the component is what
- * installed the handler being measured.
- *
- * `fireEvent.press` walks UP from the element it is handed to the nearest
- * ancestor carrying an `onPress` prop, and it does not stop at host nodes — a
- * COMPOSITE counts, because `getEventHandler` only reads `element.props`. So
- * `<Thing onPress={fn}>` written in a test's own JSX catches the press itself.
- * Measured on `ProfileCard`: with the handler deleted from the component the
- * card rendered as an inert `View`, and the test still reported exactly one
- * call. Green, and measuring nothing. Nine suites had the same shape.
- *
- * Asserting the host node's own `onPress` FIRST closes both halves:
- *
- *  - a component that installs no handler at all fails here, and
- *  - a component that installs one which drops the caller's fails on the call
- *    count, because `fireEvent` now finds a handler AT the node and never walks
- *    past it to the test's own JSX.
- *
- * `host` must therefore be the node the component itself made pressable — the
- * one carrying its `testID` / `accessibilityLabel` — not a `Text` deep inside
- * it, or the walk-up is back and so is the hole.
- */
-import { fireEvent } from '@testing-library/react-native';
-import type { ReactTestInstance } from 'react-test-renderer';
-
-export function pressHost(host: ReactTestInstance): void {
-  expect(typeof host.props.onPress).toBe('function');
-  fireEvent.press(host);
-}

package/src/__tests__/support/rendered-style.ts

@@ -1,99 +0,0 @@
-/**
- * Reading what actually landed on a rendered node — shared by every suite that
- * asserts the "className lands on the node the parent lays out" rule.
- *
- * Three components had the same two-node defect (`Button`, then `Fab` and
- * `FrostedIconButton`), and asserting it needs the same two things each time:
- * the HOST tree (composites do not appear in `toJSON()`, so a wrapper is only
- * visible there) and a deep flatten of the `style` prop, because react-native-css
- * merges a caller's class in as a `{ $$css: true, className }` descriptor
- * ALONGSIDE the style objects rather than in a prop of its own.
- */
-import type { ReactTestRendererJSON } from 'react-test-renderer';
-
-export type StyleEntry = Record<string, unknown>;
-
-export interface HostNode {
-  type: string;
-  props: Record<string, unknown>;
-  children: Array<HostNode | string> | null;
-}
-
-/**
- * Deep-flatten an RN `style` prop (nested arrays, `false`/`null` holes) into the
- * list of style objects that actually reached the node.
- */
-export function styleEntries(style: unknown, out: StyleEntry[] = []): StyleEntry[] {
-  if (!style || typeof style !== 'object') return out;
-  if (Array.isArray(style)) {
-    for (const entry of style) styleEntries(entry, out);
-    return out;
-  }
-  out.push(style as StyleEntry);
-  return out;
-}
-
-/** Every style key/value that landed on a node, later entries winning. */
-export function resolvedStyle(style: unknown): StyleEntry {
-  return Object.assign({}, ...styleEntries(style)) as StyleEntry;
-}
-
-/** The class tokens react-native-css accepted for a node, in arrival order. */
-export function classNamesOn(style: unknown): string[] {
-  return styleEntries(style)
-    .filter((entry) => entry.$$css === true && typeof entry.className === 'string')
-    .map((entry) => String(entry.className));
-}
-
-export function isHostNode(value: unknown): value is HostNode {
-  return (
-    typeof value === 'object' && value !== null && typeof (value as HostNode).type === 'string'
-  );
-}
-
-/** Walk the HOST tree (composites are absent from `toJSON()`) for a testID. */
-export function findHost(
-  node: ReactTestRendererJSON | ReactTestRendererJSON[] | unknown,
-  testID: string,
-): HostNode | null {
-  if (Array.isArray(node)) {
-    for (const child of node) {
-      const hit = findHost(child, testID);
-      if (hit) return hit;
-    }
-    return null;
-  }
-  if (!isHostNode(node)) return null;
-  if (node.props.testID === testID) return node;
-  return findHost(node.children, testID);
-}
-
-/**
- * Every host node in a rendered tree, in document order.
- *
- * The reason to walk `toJSON()` rather than `UNSAFE_root.findAll` is that the
- * latter yields COMPOSITE instances too, so a `memo(fn)` component contributes
- * two matches for one rendered element and every count is silently doubled —
- * which reads as "the component rendered the thing twice", not as an artefact
- * of the query.
- */
-export function hostNodes(tree: unknown, out: HostNode[] = []): HostNode[] {
-  if (Array.isArray(tree)) {
-    for (const child of tree) hostNodes(child, out);
-    return out;
-  }
-  if (!isHostNode(tree)) return out;
-  out.push(tree);
-  return hostNodes(tree.children, out);
-}
-
-/**
- * The host nodes a parent laid out. Callers assert the LENGTH themselves —
- * "exactly one" is the property, and a helper that returned only the first would
- * hide the second.
- */
-export function renderedChildren(tree: unknown, hostTestID: string): HostNode[] {
-  const host = findHost(tree, hostTestID);
-  if (host === null) throw new Error(`no host rendered for testID "${hostTestID}"`);
-  return (host.children ?? []).filter(isHostNode);
-}

package/src/__tests__/support/unread-hook-fixture.ts

@@ -1,33 +0,0 @@
-/**
- * A module that DELIBERATELY throws away one of the values a hook hands back, so
- * `hook-subscriptions-are-read.test.ts` can prove its detector fires. It carries
- * both halves of the control: `unreadFlag` is bound and never read, which the
- * detector must report, and `readFlag` is bound and read, which it must stay
- * quiet about — otherwise the cheapest way to green the gate would be deleting a
- * binding that is doing its job.
- *
- * Nothing imports this at runtime. bob's `exclude` keeps it out of `lib/`, and
- * `files: ["src", …]` does ship it inside the tarball's `src/` like the other
- * 137 test files there — but no entry point reaches it, so no bundler links it.
- * It is a plain `.ts` with no React import because the
- * detector reads source, never types: a call named `use…` bound to a name is all
- * the shape there is.
- *
- * The destructuring RENAMES, which is not decoration — it reproduces the shipped
- * shape (`const { state: pressed, onIn: onPressIn } = useInteractionState()`) and
- * it is what keeps the control honest. A hook declared in the same file as its
- * caller mentions its own property names in its return type and its return
- * object, and the detector counts every occurrence of a spelling as a possible
- * read, so an unrenamed fixture would be silently unreportable for a reason no
- * real call site has.
- */
-
-/** Stands in for a real subscription — a hook by name, with two return values. */
-function useFixtureInteractionState(): { first: boolean; second: boolean } {
-  return { first: false, second: false };
-}
-
-export function fixtureComponentBody(): boolean {
-  const { first: readFlag, second: unreadFlag } = useFixtureInteractionState();
-  return readFlag;
-}