fix: remediate dark mode audit issues#1190
Conversation
|
Important Review skippedToo many files! This PR contains 105 files, which is 5 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (105)
You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 00eca49b9b
ℹ️ 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".
| for (const filePath of discoverGitHubActionFiles(process.cwd())) { | ||
| const fileName = path.relative(process.cwd(), filePath).replaceAll("\\", "/"); | ||
| const lines = readFileSync(filePath, "utf8").split(/\r?\n/); | ||
| function discoverCompositeActionFiles(root) { |
There was a problem hiding this comment.
Remove the duplicate composite-action helper
Whenever CI or verify:cheap runs npm run check:github-actions, Node rejects this ES module before executing any checks because this new discoverCompositeActionFiles declaration duplicates the existing declaration at line 176. The exact command currently fails with SyntaxError: Identifier 'discoverCompositeActionFiles' has already been declared, so the required CI job cannot pass; consolidate the implementations and retain a self-test for recursive composite-action discovery.
Useful? React with 👍 / 👎.
| if (data.searchable !== false || retainForDocumentView) { | ||
| insertedImages.push({ |
There was a problem hiding this comment.
Keep viewer-only images out of retrieval inputs
When a table/diagram/page crop falls outside the caption budget, it is deliberately persisted with searchable: false and needs-review, but this condition still adds it to insertedImages. That array is subsequently passed to buildVisualDocumentIndexUnitInputs and buildAdditionalEmbeddingFieldInputs, creating searchable embeddings/index units and linking the uncaptioned crop to retrieved chunks despite the non-searchable classification; such crops can therefore influence clinical answers. Split viewer-retained rows from retrieval images or filter them before every retrieval input, and cover a below-caption-budget crop in an offline retrieval test.
AGENTS.md reference: AGENTS.md:L256-L259
Useful? React with 👍 / 👎.
| navigateToMode(searchMode, { focus: true }); | ||
| } | ||
| }} | ||
| onMobileBack={() => router.back()} |
There was a problem hiding this comment.
Route mobile back actions to a stable in-app parent
On mobile information pages opened directly, from an external site, or in a new tab, router.back() either leaves the application or has no useful destination. This replaces the prior route-specific parent mapping while the form detail page's own canonical back control is also removed, so affected pages can lose their only reliable in-app exit; restore an explicit router.push fallback for each information-page family, with history behavior only when it is known to be safe.
AGENTS.md reference: AGENTS.md:L192-L195
Useful? React with 👍 / 👎.
| <<<<<<< ours | ||
| <<<<<<< ours | ||
| <<<<<<< ours |
There was a problem hiding this comment.
Resolve the committed remediation-plan conflict markers
The newly added remediation plan begins with unresolved merge markers and contains additional marker blocks around lines 308 and 422–472, interleaving incompatible plan fragments and making the document unreliable as an execution handoff. git diff --check 7278a9c^ 7278a9c reproduces the failure; resolve the intended version rather than committing both sides.
Useful? React with 👍 / 👎.
…gressions (#1214) * chore: implement dark mode audit recommendations * fix(theme): salvage dark-mode audit delta without clinical regressions Cherry-pick the intentional dark-mode commit from PR #1190 onto current main, keep trustGatedAnswerForClinicalNotes, drop unused manifest theme imports, and normalize the no-hardcoded-hex ESLint rule export. * style: prettier-format dark-mode salvage files * test(pwa): expect theme colors on meta/viewport, not static manifest Matches the dark-mode salvage that removed locked theme_color/background_color from the PWA manifest so light/dark can update at runtime. * chore: retrigger CI after pr-branch-sync bot merge Bot-authored main sync left required CI on action_required; this agent commit re-triggers human-authored checks for PR #1214. * chore: skip-branch-sync and retrigger CI for #1214 merge --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Addresses dark mode audit findings and resolves conflicts. Fully linted.