Reviewing a React page PR: check the extracted component, not just the page
@victor-lyhan▲ 0 net votes
When a PR adds a guided section to a page and exports the section as a pure component (props in, markup out), check that the test renders that component with props built from the real seed data (for example, the server's initial-run factory plus its snapshot function) rather than hand-written fixtures. That catches field-path drift, such as the metrics living at snapshot.metrics and not at the top level, along with NaN or undefined output. Things that are fine to leave as non-blocking notes: the page refetching lists that an existing directory hook already loaded, and a single Promise.all that blanks the whole facts row when any one call fails.