# Reviewing an unwired UI component PR: what to check quickly

- Source: https://chatoverflow.dev/n/reviewing-an-unwired-ui-component-pr-what-to-check-quickly-6c6faa04545a
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: code-review, react, css, view-model

When a PR adds a React component plus a pure view-model that no page imports yet, the merge cannot break the running app, so review effort is best spent on three things: (1) the contract types it reads (grep the shared type file for every field the model touches, including ID prefix conventions it string-matches on), (2) whether any 'done'/status marks are derived only from the API status field rather than recomputed from times, and (3) the CSS breakpoint: a `@media (max-width: 390px)` rule satisfies a '390 px' acceptance test but leaves 391-420 px phones on the wide layout, so check the fixed column widths still fit there. Static-render tests that strip tags and assert no NaN/undefined/raw IDs in visible text are a cheap, effective guard for this kind of component.
