Screenshots, a README with a picture, and CONTRIBUTING.md - #36
Conversation
It ships a hardcoded half-white background, which on the dark canvas is a bright chip in the corner, sitting on top of the minimap. The rule needs !important and has to sit outside @layer base: reactflow/dist/base.css is unlayered and imported from the lazily-loaded canvas chunk, so it arrives after index.css and wins on both layering and source order. Inside the layer the rule did nothing at all.
hono's `accepts`, whose three direct calls are one exact, one name match and one unresolved -- the product's whole claim in a single frame. Two image files rather than one recoloured for the light theme. The tier colours are the subject of the picture, so an inverted dark shot would misstate them. Class-based `dark:` rather than prefers-color-scheme, because the theme toggle sets the class and the media query would ignore it.
A visual tool whose README had no picture. The same two shots, behind a <picture> so GitHub picks the one that matches the reader's theme. CONTRIBUTING covers getting it running, the checks that gate a PR, the four conventions review will ask about, and how to add a language -- including the fixture requirement, which is the reason a language ever ships silently broken.
go.mod asks for 1.25.0 and the workflow set up 1.24, so every job downloaded a second toolchain before it could build anything.
|
Warning Review limit reachedNext included review available in 51 minutes. View limit detailsLimit details: You’ve used the included review currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (8)
ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (9)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe change adds a themed canvas image to the landing page, updates React Flow attribution styling and placement, adds contributor guidance, updates release documentation, and aligns Go CI with Go 1.25. ChangesRelease polish
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This PR adds documentation, screenshots, and localized landing-page presentation updates without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review. Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/settings/billing. Comment |
Both were internal, and both had gone stale in ways a first-time reader would take as current. TASKLIST.md still opened '# Phase 5', named a branch merged three PRs ago, and told the reader that Claude implements while they review at the gate. Everything durable in it is in PLAN.md or the git history; the open items move to PLAN.md's new 'Still open' section. DEVELOPMENT.md contradicted the README and CONTRIBUTING on Node 20 vs 24, Go 1.24 vs 1.25, and listed testcontainers, which this project explicitly does not use. Its setup, checks and branching sections had become duplicates. What was unique -- driving the API by hand, checking a UI change, and the three misleading symptoms -- moves into CONTRIBUTING.md, with the curl walkthrough rewritten for single-user mode, where there is no cookie to obtain. Also corrects CANVAS_DECISIONS: a router exists now, it just does not address the selection.
1 participant
Summary by CodeRabbit
New Features
Documentation
Tests