Problem
The VS Code extension's table formatter uses a heuristic to determine whether a 2-column table should use row headers (vertical) or column headers (horizontal). This works well for data tables in steps, but Examples tables in ScenarioOutline/RuleOutline must always be horizontal — each column is a parameter name, each row is a test case.
When a ScenarioOutline has exactly 2 columns in its Examples table, the formatter may incorrectly render it as a vertical (row-header) table.
Current Implementation
\ ableFormatter/index.ts\ (line 211–238) applies the same 2-column detection logic to all tables. There is no context to distinguish Examples tables from step data tables.
Fix
The formatter should either:
- Accept a flag indicating whether the table is an Examples table (always horizontal), or
- Detect that the table appears after an \Examples:\ keyword and force horizontal layout
Examples tables should never use row-header formatting regardless of column count.
Problem
The VS Code extension's table formatter uses a heuristic to determine whether a 2-column table should use row headers (vertical) or column headers (horizontal). This works well for data tables in steps, but Examples tables in ScenarioOutline/RuleOutline must always be horizontal — each column is a parameter name, each row is a test case.
When a ScenarioOutline has exactly 2 columns in its Examples table, the formatter may incorrectly render it as a vertical (row-header) table.
Current Implementation
\ ableFormatter/index.ts\ (line 211–238) applies the same 2-column detection logic to all tables. There is no context to distinguish Examples tables from step data tables.
Fix
The formatter should either:
Examples tables should never use row-header formatting regardless of column count.