brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R15.6: Empty state affordance

Short answer: Data tables and lists display actionable empty state message. An empty table with no message looks broken.

Group: Error boundaries and fallback rendering. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R15.6

What it catches

Empty state affordance: data tables and lists display actionable empty state message.

Why

An empty table with no message looks broken.

A bad example

{rows.map(Row)}

A good example

{rows.length ? rows.map(Row) : <Empty action={<AddButton />} />}

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R15.6 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.