Skip to content

🧭 test: Cover ClickHouse Control Boundaries on the Sidebar Surface - #17197

Open
berry-13 wants to merge 1 commit into
devfrom
followup/291-pr-16821-cover-clickhouse-control-boundaries-on-
Open

berry-13 wants to merge 1 commit into
devfrom
followup/291-pr-16821-cover-clickhouse-control-boundaries-on-

Conversation

@berry-13

Copy link
Copy Markdown
Collaborator

Pull Request

Summary

The ClickHouse control-boundary check measured border-control, border-xheavy and the rings on the primary, secondary, tertiary and dialog surfaces, but not on surface-sidebar, where the sidebar's controls sit. Closes berry-13#291.

The check now includes the sidebar canvas. That surfaces four sub-floor pairs: border-control and border-xheavy on the sidebar, in light and dark. The sidebar uses Click UI's page background (#ffffff light, #1f1f1c dark), so the ratios match the surface-primary and surface-dialog pairs that are already pinned. They are added to the same Click UI pin list under the same owner decision. The palette itself does not change.

Type of change

  • Tests / tooling / CI

Testing

Tested environments/configuration:

  • Jest in packages/client

Automated tests:

  • npx jest src/theme/themes/clickhouse.spec.tsx: 56 passed. Without the four new pins, the boundary test and the pinning test fail in both modes.
  • New scenario e2e/specs/mock/scenarios/clickhouse-sidebar-boundaries.spec.ts runs the spec in file order and checks that the boundary and pinning tests pass in both modes.

Screenshots / recordings

No user-facing change.

Risk / compatibility

None. This changes tests only. #17192 restructures the same spec into a shared contrast matrix; whichever of the two merges second carries the sidebar canvas into the other's form.

Checklist

  • I reviewed my own changes
  • Relevant tests have been added or updated
  • Existing relevant tests pass
  • The change does not introduce new warnings or errors

Copilot AI balanced review requested due to automatic review settings October 16, 2026 23:02

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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@berry-13
berry-13 force-pushed the followup/291-pr-16821-cover-clickhouse-control-boundaries-on- branch from b41526e to f021fc3 Compare October 17, 2026 08:55
@berry-13
berry-13 marked this pull request as ready for review October 17, 2026 08:56
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-17T08:59:07.202960Z f021fc3 Draft marked ready
🔒 Security Review ✅ Completed 2026-10-17T08:57:42.847570Z f021fc3 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f021fc3b24

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +26 to +27
expect(output.match(/✓ keeps control boundaries and rings at the 3:1 floor/g)).toHaveLength(2);
expect(output.match(/✓ pins every pair that sits below its floor/g)).toHaveLength(2);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Assert the sidebar measurement instead of old test names

This scenario also passes against the parent revision: both matched Jest titles already existed and passed before rgb-surface-sidebar was added to the boundary background list. Removing the sidebar entry together with its four pins would therefore still produce two matches for each title, so this scenario cannot catch the exact regression it claims to cover; assert a sidebar-specific measured pair or fixture instead.

AGENTS.md reference: AGENTS.md:L53-L53

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants