Keyboard

↓ ↑
move between the rows you can see
→
open a feature, then step into it
←
close a feature, or step out to the one above
Enter
go to the page in focus
Tab
the same rows, plus everything else on the page
/
search the whole report
m
open or close the navigation drawer
Esc
leave the search box, or close the drawer
?
this list

Returns input it cannot parse unchanged

All 6 scenarios hold

Formatting must never break a build. The formatter returns input it cannot parse as a well-formed table, exactly as the author wrote it. An escaped quote is not part of the table grammar, so the formatter leaves a table holding one alone.

The first row shows the contrast. The formatter reformats parseable input, and Formatted lines then differs from Table lines.

expected outcome broken scenario
ScenarioTable linesFormatted lines?
Well-formed table
  • name|age
  • Alice|30
  • name | age
  • Alice | 30
Extra column in a data row
  • name|age
  • Alice|30
  • Bob|25|London
  • name|age
  • Alice|30
  • Bob|25|London
Missing column in a data row
  • name|age|city
  • Alice|30
  • Bob|25|London
  • name|age|city
  • Alice|30
  • Bob|25|London
Escaped quotes in a value
  • name|message
  • test|"He said \"hello\""
  • name|message
  • test|"He said \"hello\""
Empty input[][]
Whitespace-only input