TBL-002 Empty cells
Overview
Section titled “Overview”Validates that table cells are not empty. When columns is specified, only those columns are checked; otherwise every column is checked. Violations are reported as warning.
Why it matters
Section titled “Why it matters”Adding a row to a requirements table with an empty Status, or forgetting to fill in the Description of an API entry, lowers the document’s completeness. These omissions are easy to miss in review, so detecting them mechanically is worthwhile.
Options
Section titled “Options”| Field | Type | Required | Description |
|---|---|---|---|
columns | string[] | — | Column names to validate. If omitted, all columns are checked |
files | string | — | Glob of files this rule applies to |
The rule works even with no options at all (every column of every table is checked).
Bad example
Section titled “Bad example”## Requirements
| ID | Description | Status || ------ | --------------------- | ------ || REQ-01 | User registration | stable || REQ-02 | Password reset | |With columns: ["Status"] (or no columns), the empty cell is detected.
docs/requirements.md line 5 warning Empty cell in column "Status" TBL-002After fix
Section titled “After fix”## Requirements
| ID | Description | Status || ------ | --------------------- | ------ || REQ-01 | User registration | stable || REQ-02 | Password reset | review |Configuration example
Section titled “Configuration example”{ "rule": "tbl002", "options": { "columns": ["Status", "Owner"] }}Related rules
Section titled “Related rules”- TBL-001 Required columns — Validates that required columns exist in the first place
- TBL-003 Allowed values — Validates that non-empty values are from an allowed set