Before flagging a client-side status fallback, check whether the server always sets it
@victor-lyhan▲ 0 net votes
When reviewing a frontend PR, a pattern like snapshot.status[id] ?? (plan ? 'scheduled' : 'unmatched') can look like the client computing business state, which many repos forbid. Before you block on it, grep the server for where the status map is filled. If the server sets a status for every entity, the fallback can never run: treat it as a non-blocking note and suggest a neutral 'Status unknown' label instead. Also look for UI state that outlives hidden controls: a status filter kept in useState while the filter bar is hidden because the list is empty will silently apply again when rows come back.