Skip to content

refactor(app): split PalettePage into sections - #12463

Merged
MarkusNeusinger merged 5 commits into
mainfrom
gemini/palette-page-split
Oct 29, 2026
Merged

MarkusNeusinger merged 5 commits into
mainfrom
gemini/palette-page-split

Conversation

@MarkusNeusinger

@MarkusNeusinger MarkusNeusinger commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Split app/src/pages/PalettePage.tsx from 1,783 lines to 144 lines with no change in rendered markup, text, styles, or behaviour.
  • Extracted the palette page types (CompPalette, Anchor, HistoryEntry, WheelDot) into app/src/sections/palette/types.ts and the colour helpers (oklchToRgb, starPoints, textOn, deltaECellBg) plus shared non-component constants (COMPARISONS, tooltipSlotProps, sectionSx, proseColumnSx) into app/src/sections/palette/paletteHelpers.ts so every .tsx file exports only its component and satisfies react-refresh/only-export-components.
  • Extracted the three inline helper components into app/src/sections/palette/ChromaWheel.tsx, app/src/sections/palette/CodeBlock.tsx, and app/src/sections/palette/DeltaEMatrix.tsx.
  • Extracted all eight numbered sections into app/src/sections/palette/HeroSection.tsx, app/src/sections/palette/PaletteGridSection.tsx, app/src/sections/palette/SemanticAnchorsSection.tsx, app/src/sections/palette/ContinuousCmapsSection.tsx, app/src/sections/palette/CopySnippetsSection.tsx, app/src/sections/palette/WcagContrastSection.tsx, app/src/sections/palette/DeltaESection.tsx, and app/src/sections/palette/LineageSection.tsx.
  • Added the changelog fragment changelog.d/palette-page-split.md. No files outside the brief's Constraints were touched.
  • Provenance and review. Implemented by Gemini 4 Argon in the owner's interactive agy session from a brief file (the first run of the brief lane, docs(gemini-task): hand Gemini briefs instead of issues #12458), and reviewed by Claude. A fresh Opus reviewer compared all 32 top-level declarations and the eight section blocks against the original with the TypeScript parser: no behaviour defects; cosmetic only (Prettier split one text node in WcagContrastSection.tsx into two adjacent ones with the same text, and an obsolete "Inline sub-components" banner comment went with the components it labelled). No fix commits were needed; Claude only added the PR reference to the fragment. For comparison, none of the three Jules variants of this split on 2026-10-29 kept the page intact.

Plan

Brief palette-page-split, package 1 of 1, as written:

Brief

Split PalettePage into sections without changing what it renders

Branch gemini/palette-page-split · package 1 of 1

Goal

app/src/pages/PalettePage.tsx is 1,783 lines: three helper components, four
colour helpers, and one page component with eight numbered sections. Split it
the way DebugPage and MapPage were split (PR #12457), so each section lives in
its own file under app/src/sections/palette/ and the page keeps only state,
effects, and layout. This is a pure refactor: the rendered page, its text, its
markup, and its behaviour stay exactly the same.

Context

  • Models to follow: app/src/sections/debug/ and app/src/sections/map/
    (one component per file, named exports, shared helpers in a non-component
    module such as app/src/sections/debug/debugFormat.ts).
  • The page's numbered sections (comments in the JSX): 1. hero with the
    hue–chroma wheel, 2. palette grid and sort toggle, 3. semantic anchors,
    3b. continuous cmaps, 4. copy snippets, 5. WCAG contrast, 6. ΔE colour
    distance, 7. lineage. Helper components: ChromaWheel, CodeBlock,
    DeltaEMatrix. Helpers: oklchToRgb, starPoints, textOn,
    deltaECellBg. Types: CompPalette, Anchor, HistoryEntry, WheelDot.
  • app/src/pages/PalettePage.helpers.ts and
    app/src/pages/PalettePage.snippet.test.ts already exist and stay as they are.
  • An earlier attempt by another agent failed in ways to avoid: it dropped
    whole sections, cut JSX apart with string slicing so elements lost their
    closing tags, invented markup (a solid separator where a dashed border was),
    typed props as any behind eslint-disable comments, and committed helper
    scripts. Claude will compare the rendered page against main element by
    element, so any visible change will be found.

Steps

  • Move the types and the four colour helpers into
    app/src/sections/palette/ (a types module and a non-component helpers
    module; a component file that also exports functions breaks React fast
    refresh and fails lint).
  • Move ChromaWheel, CodeBlock, and DeltaEMatrix into their own files.
  • Move each numbered section into its own component file; the page passes
    the state and handlers it owns as typed props.
  • Add the changelog fragment.

Constraints

  • Move code verbatim: whole declarations and complete JSX elements, copied as
    text with your edit tool. No regex, sed, or script-based slicing, and no
    helper scripts in the repository.
  • Keep every comment with the code it describes.
  • Change no markup, style, text, element order, or behaviour, not even an
    obvious improvement. State, effects, and memos stay in PalettePage; add no
    new hooks.
  • No any and no eslint-disable anywhere; type props with the existing
    types.
  • Touch only app/src/pages/PalettePage.tsx, new files under
    app/src/sections/palette/, and one fragment under changelog.d/.

Acceptance

All of these, run from the repository root of the clone:

cd app && yarn lint && yarn fm:check && yarn type-check && yarn test && yarn build && cd ..

Each convention check below must print nothing:

git diff --name-only origin/main...HEAD | grep -v -E '^(app/src/pages/PalettePage\.tsx|app/src/sections/palette/|changelog\.d/)'
grep -rn -E 'eslint-disable|: any\b|as any|<any>' app/src/pages/PalettePage.tsx app/src/sections/palette/
[ "$(wc -l < app/src/pages/PalettePage.tsx)" -le 450 ] || echo "PalettePage.tsx is still too long"

yarn lint must report no warnings, not only no errors.

Decide yourself / report back

  • Decide yourself: file and prop names, how to group the helpers and types,
    and whether a very small section stays inline in the page. Document the
    choices in the hand-over.
  • Report back instead of guessing: any code that cannot move without a change
    in markup or behaviour, and any existing test that would need more than an
    import change.

Test plan

  • cd app && yarn lint — Done in 8.38s. (0 errors, 0 warnings)

  • cd app && yarn fm:check — All matched files use Prettier code style!

  • cd app && yarn type-check — Done in 4.12s.

  • cd app && yarn test — Test Files 113 passed (113), Tests 1197 passed (1197)

  • cd app && yarn build — Done in 5.59s.

  • PYTHON_DOTENV_DISABLED=1 uv run python -m tools.changelog check --base origin/main — the diff against origin/main passes the fragment rule

  • Convention checks:

    • git diff --name-only origin/main...HEAD | grep -v -E '^(app/src/pages/PalettePage\.tsx|app/src/sections/palette/|changelog\.d/)' (empty output)
    • grep -rn -E 'eslint-disable|: any\b|as any|<any>' app/src/pages/PalettePage.tsx app/src/sections/palette/ (empty output)
    • [ "$(wc -l < app/src/pages/PalettePage.tsx)" -le 450 ] || echo "PalettePage.tsx is still too long" (empty output; PalettePage.tsx is 144 lines)
  • Claude: /palette built from main and from this branch against the production API, clicked through ten states (load, wheel expanded, two comparison palettes, CVD sort, two language tabs, OKLCH on, copy a swatch, wheel collapsed): <main> HTML byte-identical at every step, emotion class names included (they hash the styles), no page errors

  • Claude: frontend gates on the branch (lint without warnings, Prettier, type-check, 1,210 tests, build)

  • codecov/patch/frontend stays red: the page never had render tests, and moved code counts as new; section render tests are the next Gemini task

Decisions

  • Grouping of helpers and types: Created app/src/sections/palette/types.ts for CompPalette, Anchor, HistoryEntry, and WheelDot, and app/src/sections/palette/paletteHelpers.ts for the four colour helpers (oklchToRgb, starPoints, textOn, deltaECellBg), ΔE thresholds (DE_T_BAD, DE_T_WARN, DE_T_OK), shared comparison palettes (COMPARISONS), and shared layout/tooltip style constants (tooltipSlotProps, sectionSx, proseColumnSx) so .tsx component files export only components.
  • Section granularity and file names: Extracted all eight numbered sections into dedicated component files (HeroSection.tsx, PaletteGridSection.tsx, SemanticAnchorsSection.tsx, ContinuousCmapsSection.tsx, CopySnippetsSection.tsx, WcagContrastSection.tsx, DeltaESection.tsx, LineageSection.tsx), co-locating each section's private data constants (HYBRID_V3_CVD, PURE_CVD_GREEDY, ANCHORS, LANG_LABELS, WCAG_TABLE, DE_LEGEND, HISTORY) inside the section component that renders them.

Open steps and questions

  • None

MarkusNeusinger and others added 4 commits October 30, 2026 00:01
Step 1 of 4: move CompPalette, Anchor, HistoryEntry, and WheelDot into
app/src/sections/palette/types.ts, and oklchToRgb, starPoints, textOn,
and deltaECellBg into app/src/sections/palette/paletteHelpers.ts.

Brief: palette-page-split

Co-Authored-By: Antigravity (Gemini 4 Argon) <noreply@google.com>
Step 2 of 4: move ChromaWheel, CodeBlock, and DeltaEMatrix into their
own component files under app/src/sections/palette/, sharing
tooltipSlotProps from paletteHelpers.ts.

Brief: palette-page-split

Co-Authored-By: Antigravity (Gemini 4 Argon) <noreply@google.com>
Step 3 of 4: extract HeroSection, PaletteGridSection,
SemanticAnchorsSection, ContinuousCmapsSection, CopySnippetsSection,
WcagContrastSection, DeltaESection, and LineageSection under
app/src/sections/palette/, leaving PalettePage with state, effects,
memos, and layout (144 lines).

Brief: palette-page-split

Co-Authored-By: Antigravity (Gemini 4 Argon) <noreply@google.com>
Step 4 of 4: add changelog.d/palette-page-split.md.

Brief: palette-page-split

Co-Authored-By: Antigravity (Gemini 4 Argon) <noreply@google.com>
@MarkusNeusinger MarkusNeusinger added the gemini Task for Gemini in the owner's interactive agy session (gemini-task skill) label Oct 29, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MarkusNeusinger
MarkusNeusinger marked this pull request as ready for review October 29, 2026 23:37
Copilot AI lite review requested due to automatic review settings October 29, 2026 23:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The change still has an active moderate finding because the extracted palette rendering and interaction paths lack focused tests, leaving frontend patch coverage failing.

1 open issue
What changed in this PR

This pull request refactors PalettePage into focused palette sections and shared helper modules while preserving its rendered output and behavior. The extracted rendering and interaction paths currently lack focused component/page tests, leaving frontend patch coverage red.

Changes:

  • Reduced PalettePage.tsx to state, effects, derived data, metadata, and section composition.
  • Extracted eight sections and three helper components under app/src/sections/palette/.
  • Centralized palette types, constants, color helpers, thresholds, and shared styles.
  • Added a changelog fragment.
  • Focused tests are still needed for the wheel, sorting, copying, tabs/OKLCH controls, and theme-dependent WCAG rendering.
File Description
changelog.d/​palette-page-split.md Documents the PalettePage section split.
app/​src/​sections/​palette/​WcagContrastSection.tsx Renders the theme-aware WCAG contrast table.
app/​src/​sections/​palette/​types.ts Defines shared palette, anchor, lineage, and wheel types.
app/​src/​sections/​palette/​SemanticAnchorsSection.tsx Renders semantic anchor swatches and copy interactions.
app/​src/​sections/​palette/​paletteHelpers.ts Provides shared palette data, color helpers, thresholds, and layout styles.
app/​src/​sections/​palette/​PaletteGridSection.tsx Renders categorical swatches, sorting controls, tooltips, and copy actions.
app/​src/​sections/​palette/​LineageSection.tsx Renders palette history and provenance information.
app/​src/​sections/​palette/​HeroSection.tsx Renders the palette hero, wheel, and comparison controls.
app/​src/​sections/​palette/​DeltaESection.tsx Renders ΔE explanations, matrices, and the legend.
app/​src/​sections/​palette/​DeltaEMatrix.tsx Provides the reusable ΔE matrix renderer.
app/​src/​sections/​palette/​CopySnippetsSection.tsx Renders language tabs, the OKLCH toggle, and code snippets.
app/​src/​sections/​palette/​ContinuousCmapsSection.tsx Renders sequential and diverging continuous colormap previews.
app/​src/​sections/​palette/​CodeBlock.tsx Provides the copyable code block component.
app/​src/​sections/​palette/​ChromaWheel.tsx Provides the interactive hue–chroma wheel.
app/​src/​pages/​PalettePage.tsx Retains page state, effects, memoized data, metadata, and section composition.

Review effort: Lite

Comment thread app/src/pages/PalettePage.tsx Resolved
@MarkusNeusinger
MarkusNeusinger merged commit e88a83d into main Oct 29, 2026
18 of 19 checks passed
@MarkusNeusinger
MarkusNeusinger deleted the gemini/palette-page-split branch October 29, 2026 23:53
MarkusNeusinger added a commit that referenced this pull request Oct 30, 2026
)

## Summary
- Add co-located unit and render tests in `app/src/sections/palette/`
(`paletteHelpers.test.ts`, `ChromaWheel.test.tsx`, `CodeBlock.test.tsx`,
`DeltaEMatrix.test.tsx`, `HeroSection.test.tsx`,
`PaletteGridSection.test.tsx`, `SemanticAnchorsSection.test.tsx`,
`ContinuousCmapsSection.test.tsx`, `CopySnippetsSection.test.tsx`,
`WcagContrastSection.test.tsx`, `DeltaESection.test.tsx`,
`LineageSection.test.tsx`) covering the helpers, canvas wheel, and eight
section components extracted from `PalettePage` in PR #12463.
- Add co-located unit and render tests in `app/src/sections/debug/`
(`debugFormat.test.ts`, `SpecMatrix.test.tsx`,
`FeedbackSection.test.tsx`, `DebugOverviewSections.test.tsx`) covering
`debugFormat.ts`, `constants.ts`, `HeaderCell`, `SortableHeader`,
`SpecMatrix`, `FeedbackSection`, `FeedbackTopList`,
`CopyClaudePromptButton`, `SystemHealthRow`, `KPIGrid`,
`DailyActivityChart`, `LibraryCoverage`, `RecentActivity`,
`CommonWeaknesses`, and `ProblemAreas` extracted from `DebugPage` in PR
#12457.
- Add co-located render and interaction tests in `app/src/sections/map/`
(`MapLegend.test.tsx`, `MapHoverPanel.test.tsx`, `MapWeights.test.tsx`,
`MapSearchPill.test.tsx`, `MapCanvas.test.tsx`) covering the five map
components extracted from `MapPage` in PR #12457.
- Add `changelog.d/section-tests.md` for the integrated task
(`tools.changelog check` gate). Apart from the two page test files that
review round 1 allowed, only `*.test.ts` / `*.test.tsx` files under the
three section folders changed; no component changed.test.ts` /
`*.test.tsx` constraints were touched.
- Add page-level tests for the state that lives in the pages, from
review round 1: `app/src/pages/PalettePage.test.tsx` (new: swatch copy
reset at the 1,499/1,500 ms boundary, CVD sort order, wheel, comparison,
tabs, OKLCH, pageview) and new tests in
`app/src/pages/DebugPage.test.tsx` (sort orders per header and
direction, incomplete and low-score filters, feedback status PATCH with
`X-Admin-Token`, revert on 500, status-filter refetch). The section
tests now assert their prop contracts instead of re-implementing page
logic.
- **Provenance:** implemented by Gemini 4 Argon in the owner's
interactive agy session, the first brief-lane task run as parallel agy
subagents (three packages, each in its own worktree), and reviewed by
Claude. Claude's checks: every Acceptance command per package, plus
independent Opus reviews that broke behaviours on purpose. [Review round
1](#12470 (comment))
found that the palette and debug tests re-implemented the pages' sort,
filter, copy-reset, and PATCH logic in test harnesses and tested that
copy; Gemini fixed it in merges 8de98c6, 63ae112, and 3d884c3 and
reported the mutation results. Claude closed the remaining gaps in
7c1ce5a: the per-theme WCAG swatch stroke (tested through the declared
stylesheet rule, since jsdom drops `var()` borders), a low-score fixture
that could not tell a library score from the average, and a select value
on rerender. All 14 mutations from the review behave as the review
expects (13 turn a test red, the harmless refactor stays green), and so
do the two Claude added for these gaps.

## Plan
Task `section-tests` across 3 packages:
- **Package 1 of 3 (`section-tests-1`)** — branch
`gemini/section-tests-1`, last commit
`2ff23e5bb7fcd149654f093c583999a455a7fc0c`, merge commit
`549441523f96068b24c7d7cc7987e3a0a03d3c60`
- **Package 2 of 3 (`section-tests-2`)** — branch
`gemini/section-tests-2`, last commit
`2f6121f390e4f08d7674b9d445bacf9a65081721`, merge commit
`e9b3b723000a9ee97b47241ff6799d45ce01b075`
- **Package 3 of 3 (`section-tests-3`)** — branch
`gemini/section-tests-3`, last commit
`46458a4efcc802c50e84c7085547684f653bd3c4`, merge commit
`389f48de5a5bb961672e37c8fd4f8adf1ce1c4c9`

<details><summary>Brief: section-tests-1 (package 1 of 3)</summary>

# Add render tests for the palette sections

Branch `gemini/section-tests-1` (independent) · package 1 of 3

## Goal

`app/src/sections/palette/` (split out of PalettePage in PR #12463) has
no
render tests, so the moved code counts as uncovered and the
`codecov/patch/frontend` check stays red. Add focused tests that render
each
section and exercise its controls, so a later change that breaks the
page
fails a test.

## Context

- Files: `ChromaWheel.tsx`, `CodeBlock.tsx`, `DeltaEMatrix.tsx`,
`HeroSection.tsx`, `PaletteGridSection.tsx`,
`SemanticAnchorsSection.tsx`,
  `ContinuousCmapsSection.tsx`, `CopySnippetsSection.tsx`,
  `WcagContrastSection.tsx`, `DeltaESection.tsx`, `LineageSection.tsx`,
`paletteHelpers.ts`, `types.ts`; the page is
`app/src/pages/PalettePage.tsx`.
- Test patterns to follow:
`app/src/sections/map/useMapSelection.test.tsx`
  and `app/src/sections/map/useMapResize.test.tsx` (stubs, fake timers),
`app/src/pages/MapPage.test.tsx` (stubbing globals and restoring them in
  `afterEach`), and the existing tests under `app/src/sections/debug/`.
- Interactions worth a test: expanding and collapsing the hue–chroma
wheel and
  its `aria-expanded`, picking and unpicking a comparison palette
(`aria-pressed`), switching the sort between imprint and CVD order,
copying
a swatch (clipboard stub, the copied feedback, and its reset after 1500
ms
  with fake timers), the language tabs and the OKLCH switch changing the
snippet text, and the light and dark theme variants where a section
reads
  `isDark`.
- Package 2 (debug) and package 3 (map) run in parallel in other
worktrees;
  they touch only their own folders.

## Steps

- [ ] Tests for the helpers in `paletteHelpers.ts` (pure functions).
- [ ] Render tests for `ChromaWheel`, `CodeBlock`, and `DeltaEMatrix`.
- [ ] Render and interaction tests for the eight section components.

## Constraints

- Add only new `*.test.ts` or `*.test.tsx` files next to the code under
`app/src/sections/palette/`. Change no component; if one cannot be
tested
  without a change, report it instead of changing it.
- Assert on what a user sees (text, roles, `aria-*` attributes), not on
class
  names or emotion hashes.
- Restore every stubbed global and timer in `afterEach`, so other suites
stay
  clean.
- No `any`, no `eslint-disable`, no snapshot files.
- No changelog fragment and no PR: the coordinator merges the packages
and
  writes one fragment for the task.

## Acceptance

Run each command on its own, from `app/`:

```bash
yarn test
yarn lint
yarn fm:check
yarn type-check
yarn vitest run --coverage --coverage.include='src/sections/palette/**' src/sections/palette
```

The coverage summary for `All files` shows at least 80 % of lines. `yarn
lint`
reports no warnings. From the clone root, each of these prints nothing:

```bash
git diff --name-only origin/main...HEAD -- . ':!app/src/sections/palette/*.test.ts' ':!app/src/sections/palette/*.test.tsx'
grep -rn -E 'eslint-disable|: any\b|as any|<any>' app/src/sections/palette --include=*.test.ts --include=*.test.tsx
```

## Decide yourself / report back

- Decide yourself: how to group tests into files, test names, and which
  helper stubs to share within this folder. Document the choices.
- Report back instead of guessing: a component that needs a change to be
  testable, and any test that only passes with a timing workaround.

</details>

<details><summary>Brief: section-tests-2 (package 2 of 3)</summary>

# Add render tests for the debug sections split out of DebugPage

Branch `gemini/section-tests-2` (independent) · package 2 of 3

## Goal

PR #12457 moved DebugPage's blocks into `app/src/sections/debug/`
without
render tests for them, so the moved code counts as uncovered. Add
focused tests
that render each of those components and exercise their controls, so a
later
change that breaks the debug page fails a test.

## Context

- The files to cover (all in `app/src/sections/debug/`):
`CommonWeaknesses.tsx`,
`CopyClaudePromptButton.tsx`, `DailyActivityChart.tsx`,
`FeedbackSection.tsx`,
`FeedbackTopList.tsx`, `HeaderCell.tsx`, `KPIGrid.tsx`,
`LibraryCoverage.tsx`,
  `ProblemAreas.tsx`, `RecentActivity.tsx`, `SortableHeader.tsx`,
`SpecMatrix.tsx`, `SystemHealthRow.tsx`, `debugFormat.ts`,
`constants.ts`.
The other files in the folder (agent cases, promote, tags, diff, triage)
  already have their own tests and are out of scope.
- Data shapes and realistic mock values:
`app/src/pages/DebugPage.test.tsx`
  (its mock API payload) and the exported types in each section file.
- Interactions worth a test: sorting `SpecMatrix` by each sortable
column and
direction (`SortableHeader`), the incomplete and low-score filters, the
  feedback status filter and status changes in `FeedbackSection` (stub
`fetchWithAuth` the way `DebugPage.test.tsx` does), the clipboard button
with
its feedback, and the colour thresholds in `debugFormat.ts`
(`scoreColor`,
  `pingColor`, `formatNum`, `formatDateShort`, `countImpls`).
- Test patterns: the existing tests in this folder and
  `app/src/sections/map/useMapSelection.test.tsx`.
- Package 1 (palette) and package 3 (map) run in parallel in other
worktrees;
  they touch only their own folders.

## Steps

- [ ] Tests for `debugFormat.ts`.
- [ ] Render tests for the table and header components (`SpecMatrix`,
      `SortableHeader`, `HeaderCell`) with sorting and filters.
- [ ] Render tests for the remaining sections listed under Context.

## Constraints

- Add only new `*.test.ts` or `*.test.tsx` files under
`app/src/sections/debug/`. Change no component and no existing test; if
a
  component cannot be tested without a change, report it instead.
- Assert on what a user sees (text, roles, `aria-*` attributes), not on
class
  names or emotion hashes.
- Restore every stubbed global, fetch, and timer in `afterEach`.
- No `any`, no `eslint-disable`, no snapshot files.
- No changelog fragment and no PR: the coordinator merges the packages
and
  writes one fragment for the task.

## Acceptance

Run each command on its own, from `app/`:

```bash
yarn test
yarn lint
yarn fm:check
yarn type-check
yarn vitest run --coverage --coverage.include='src/sections/debug/**' src/sections/debug
```

In the coverage table, every file listed under Context shows at least 80
% of
lines. `yarn lint` reports no warnings. From the clone root, each of
these
prints nothing:

```bash
git diff --name-only origin/main...HEAD -- . ':!app/src/sections/debug/*.test.ts' ':!app/src/sections/debug/*.test.tsx'
git diff --name-only --diff-filter=M origin/main...HEAD
grep -rn -E 'eslint-disable|: any\b|as any|<any>' app/src/sections/debug --include=*.test.ts --include=*.test.tsx
```

## Decide yourself / report back

- Decide yourself: how to group tests into files, test names, and shared
  mock data within this folder. Document the choices.
- Report back instead of guessing: a component that needs a change to be
  testable, and any test that only passes with a timing workaround.

</details>

<details><summary>Brief: section-tests-3 (package 3 of 3)</summary>

# Add render tests for the map components split out of MapPage

Branch `gemini/section-tests-3` (independent) · package 3 of 3

## Goal

PR #12457 moved MapPage's markup into `app/src/sections/map/`. Its three
hooks
have tests, but the five components do not, so the moved code counts as
uncovered. Add focused render tests for them, so a later change that
breaks
the map fails a test.

## Context

- The files to cover (all in `app/src/sections/map/`):
`MapHoverPanel.tsx`,
`MapLegend.tsx`, `MapSearchPill.tsx`, `MapWeights.tsx`, `MapCanvas.tsx`.
The
hooks (`useMapSelection`, `useMapSearch`, `useMapResize`) already have
tests
  and are out of scope.
- `app/src/pages/MapPage.test.tsx` shows how to stub
`react-force-graph-2d`,
  `ResizeObserver`, `src/hooks`, `src/hooks/useLayoutContext`, and
`@mui/material/useMediaQuery`. Types: `MapGraphData` and
`MapForceConfig` in
  `app/src/hooks/useForceGraphSimulation.ts`, `MapNode` in
  `app/src/pages/MapPage.helpers.ts`, `MapPanelData` in
  `app/src/sections/map/useMapSelection.ts`.
- Interactions worth a test: the legend's open and closed state and its
entries per top type; the hover panel for a hovered versus a pinned
node,
  with and without a preview image; the search pill's results, keyboard
  navigation, and selection callback; the weight sliders and the edge
threshold calling their setters, and the reset button; for `MapCanvas`,
the
loading gate before `ready`, the progress text while settling, and that
the
  stubbed ForceGraph2D receives the graph data and the click and hover
  handlers. The canvas paint callbacks themselves need no pixel tests.
- Package 1 (palette) and package 2 (debug) run in parallel in other
  worktrees; they touch only their own folders.

## Steps

- [ ] Render tests for `MapLegend`, `MapHoverPanel`, and `MapWeights`.
- [ ] Render and keyboard tests for `MapSearchPill`.
- [ ] Render tests for `MapCanvas` with ForceGraph2D stubbed.

## Constraints

- Add only new `*.test.tsx` files under `app/src/sections/map/`. Change
no
component and no existing test; if a component cannot be tested without
a
  change, report it instead.
- Assert on what a user sees (text, roles, `aria-*` attributes) and on
the
props the ForceGraph2D stub receives, not on class names or emotion
hashes.
- Restore every stubbed global and timer in `afterEach`.
- No `any`, no `eslint-disable`, no snapshot files.
- No changelog fragment and no PR: the coordinator merges the packages
and
  writes one fragment for the task.

## Acceptance

Run each command on its own, from `app/`:

```bash
yarn test
yarn lint
yarn fm:check
yarn type-check
yarn vitest run --coverage --coverage.include='src/sections/map/Map*.tsx' src/sections/map
```

In the coverage table, `MapCanvas.tsx` shows at least 50 % of lines (its
paint
callbacks run only on a real canvas) and every other component at least
80 %.
`yarn lint` reports no warnings. From the clone root, each of these
prints
nothing:

```bash
git diff --name-only origin/main...HEAD -- . ':!app/src/sections/map/*.test.tsx'
git diff --name-only --diff-filter=M origin/main...HEAD
grep -rn -E 'eslint-disable|: any\b|as any|<any>' app/src/sections/map --include=*.test.tsx
```

## Decide yourself / report back

- Decide yourself: how to group tests into files, test names, and shared
  fixtures within this folder. Document the choices.
- Report back instead of guessing: a component that needs a change to be
  testable, and any test that only passes with a timing workaround.

</details>

## Test plan
- [x] `cd app && yarn test` — `Test Files 134 passed (134)`, `Tests 1284
passed (1284)`
- [x] `cd app && yarn lint` — `Done` (0 errors, 0 warnings)
- [x] `cd app && yarn fm:check` — `All matched files use Prettier code
style!`
- [x] `cd app && yarn type-check` — `Done` (0 errors)
- [x] `cd app && yarn build` — `✓ 1939 modules transformed`, `Done`
- [x] `cd app && yarn vitest run --coverage
--coverage.include='src/sections/palette/**' src/sections/palette` —
`All files: 98.88% Stmts | 96.82% Branch | 100% Funcs | 100% Lines` (12
test files, 32 tests)
- [x] `cd app && yarn vitest run --coverage
--coverage.include='src/sections/debug/**' src/sections/debug` — 100%
Lines on all 15 target files (`CommonWeaknesses.tsx`,
`CopyClaudePromptButton.tsx`, `DailyActivityChart.tsx`,
`FeedbackSection.tsx`, `FeedbackTopList.tsx`, `HeaderCell.tsx`,
`KPIGrid.tsx`, `LibraryCoverage.tsx`, `ProblemAreas.tsx`,
`RecentActivity.tsx`, `SortableHeader.tsx`, `SpecMatrix.tsx`,
`SystemHealthRow.tsx`, `constants.ts`, `debugFormat.ts`)
- [x] `cd app && yarn vitest run --coverage
--coverage.include='src/sections/map/Map*.tsx' src/sections/map` —
`MapCanvas.tsx`: 64.64% Lines; `MapHoverPanel.tsx`, `MapLegend.tsx`,
`MapSearchPill.tsx`, `MapWeights.tsx`: 100% Lines (8 test files, 37
tests)
- [x] `git diff --name-only origin/main...origin/gemini/section-tests-1
-- . ':!app/src/sections/palette/*.test.ts'
':!app/src/sections/palette/*.test.tsx'` — empty output
- [x] `git diff --name-only origin/main...origin/gemini/section-tests-2
-- . ':!app/src/sections/debug/*.test.ts'
':!app/src/sections/debug/*.test.tsx'` — empty output
- [x] `git diff --name-only --diff-filter=M
origin/main...origin/gemini/section-tests-2` — empty output
- [x] `git diff --name-only origin/main...origin/gemini/section-tests-3
-- . ':!app/src/sections/map/*.test.tsx'` — empty output
- [x] `git diff --name-only --diff-filter=M
origin/main...origin/gemini/section-tests-3` — empty output
- [x] `grep -rn -E 'eslint-disable|: any\b|as any|<any>'
app/src/sections/palette --include=*.test.ts --include=*.test.tsx` —
empty output
- [x] `grep -rn -E 'eslint-disable|: any\b|as any|<any>'
app/src/sections/debug --include=*.test.ts --include=*.test.tsx` — empty
output
- [x] `grep -rn -E 'eslint-disable|: any\b|as any|<any>'
app/src/sections/map --include=*.test.tsx` — empty output
- [x] `PYTHON_DOTENV_DISABLED=1 uv run python -m tools.changelog check
--base origin/main` — `68 fragment(s) well-formed ... the diff against
origin/main passes the fragment rule`

## Decisions
- **Package 1 (`app/src/sections/palette/`)**: Placed one co-located
test file next to each module (`paletteHelpers.test.ts`,
`ChromaWheel.test.tsx`, `CodeBlock.test.tsx`, `DeltaEMatrix.test.tsx`,
`HeroSection.test.tsx`, `PaletteGridSection.test.tsx`,
`SemanticAnchorsSection.test.tsx`, `ContinuousCmapsSection.test.tsx`,
`CopySnippetsSection.test.tsx`, `WcagContrastSection.test.tsx`,
`DeltaESection.test.tsx`, `LineageSection.test.tsx`). Used lightweight
stateful test harnesses for controlled parent props (`wheelOpen`,
`compareId`, `sort`, `copiedHex` + 1500 ms timer reset, `lang`, `oklch`)
and a 64x64 2D canvas context stub in `ChromaWheel.test.tsx`
(`createImageData` / `putImageData`) to exercise the pixel hue-ring
painter and cache.
- **Package 2 (`app/src/sections/debug/`)**: Grouped the 15 target
modules into four focused suites: `debugFormat.test.ts` (formatting and
colour thresholds), `SpecMatrix.test.tsx` (`HeaderCell`,
`SortableHeader`, and `SpecMatrix` sorting and filters),
`FeedbackSection.test.tsx` (`FeedbackSection`, `FeedbackTopList`,
`CopyClaudePromptButton`, and `constants.ts` with `fetch` stubbed via
`vi.stubGlobal`), and `DebugOverviewSections.test.tsx`
(`SystemHealthRow`, `KPIGrid`, `DailyActivityChart`, `LibraryCoverage`,
`RecentActivity`, `CommonWeaknesses`, and `ProblemAreas`).
- **Package 3 (`app/src/sections/map/`)**: Placed one co-located test
file per component (`MapLegend.test.tsx`, `MapHoverPanel.test.tsx`,
`MapWeights.test.tsx`, `MapSearchPill.test.tsx`, `MapCanvas.test.tsx`)
with inline typed fixture builders (`makeGraphData`, `makePanelData`,
`SearchPillHarness`, `makeNode`, `makeForceConfig`, `makeProps`) so only
`*.test.tsx` files were added.

## Open steps and questions
- None.

---------

Co-authored-by: Antigravity (Gemini 4 Argon) <noreply@google.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gemini Task for Gemini in the owner's interactive agy session (gemini-task skill)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants