To Table¶
Overview¶
Data can be split on different characters and rendered as an HTML, ASCII or Markdown table with an optional header row.
Supports the CSV (Comma Separated Values) file format by default. Change the cell delimiter argument to \t to support TSV (Tab Separated Values) or | for PSV (Pipe Separated Values).
You can enter as many delimiters as you like. Each character will be treat as a separate possible delimiter.
Status¶
| Field | Value |
|---|---|
| Implementation | Partial |
| Parity | Unknown |
| Availability | Available |
| Input requirement | Required |
| Features | none |
| Side effects | [] |
| Deterministic | true |
Input¶
Declared input type: String.
Output¶
Declared output type: HTML. Redirect stdout or use --output-file for exact binary bytes.
Arguments¶
| # | Argument | Type | Required | Default | Allowed | Sensitive | Description |
|---|---|---|---|---|---|---|---|
| 1 | Cell delimiters | String |
no | , |
— | no | Characters used to separate cells |
| 2 | Row delimiters | String |
no | \\r\\n |
— | no | Characters used to separate rows |
| 3 | Make first row header | Boolean |
no | false |
— | no | Treat the first row as a header row |
| 4 | Format | String |
no | ASCII |
— | no | The output format |
Implementation¶
The implementation is in src/operations/to_table.rs and declares String input and HTML output. The operation module owns conversion and domain-error rules; registry resolution, argument validation, input-requirement enforcement, tracing, and output validation are performed by rxchef::execution.
Command-line use¶
This operation requires input. Supply literal UTF-8 with --input, exact bytes with --input-file, or pipe bytes on stdin.
rxchef run "To Table" --input-file input.bin --output-file output.bin
Arguments may be supplied positionally in the table order or by name with repeatable --arg NAME=VALUE. Omitted optional arguments use the documented defaults.
Pipeline use¶
Place the operation anywhere a String value is valid. Its HTML result becomes the next step's input. Compact syntax uses the operation name followed by comma-separated arguments; JSON/YAML recipes use an op field and an args array.
Error conditions¶
Schema violations are rejected before the operation runs. Malformed input, unsupported parameter combinations, unavailable optional backends, and domain processing failures produce structured errors and a non-zero CLI status; partial output is never reported as success.
CyberChef compatibility¶
Parity status: Unknown. Unknown records an unassessed compatibility claim; it does not imply equality or incompatibility.
Security considerations¶
Declared side effects: []. Treat parser inputs as untrusted and apply execution limits to large data. Arguments marked sensitive in the schema are redacted from metadata-aware History displays.
Testing evidence¶
Correctness tests: - tests/tests/operations/to_table.rs
Differential tests: - tests/tests/differential.rs
Performance classification¶
Excluded from the committed representative benchmark set: No stable representative benchmark case is defined; operation remains Partial until performance evidence is reviewed.