Convert YAML to TSV
Turn YAML files into TSV. A list of objects becomes one row per object under a header of every key in first-seen order, and a single object becomes one row.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop YAML files on the dialor turn it to pick what to do
A table from your YAML list.Each object becomes a row, with one column for every key.
What you get
One TSV file. A list of objects becomes one row per object, under a header that holds every key in the order it first appears. A single object becomes one row.
If the YAML has several documents, they are treated as a list, so each document adds a row.
How values are written
Nested objects and lists are written into their cell as JSON text. A null value leaves the cell empty. A cell that holds a tab, a quote or a line break is quoted.
Values such as yes, on, 0755 and dates stay text, exactly as they are written in the YAML.
What changes
Aliases are expanded, so each place that used an alias gets the full value. Comments are dropped.
A merge key (<<) is not merged. It is kept as an ordinary key, so it gets its own column.
When it stops
If the file cannot be parsed, the conversion stops with
input_corrupted. To go the other way, use TSV to YAML.
YAML and TSV.What each format is.
The formats
YAML
YAML configuration and data files.
- Extensions
- .yaml .yml
- MIME type
- application
/yaml - Kind
- Text and data
Tab-Separated Values
Tab-separated values.
- Extensions
- .tsv .tab
- MIME type
- text
/tab -separated -values - Kind
- Text and data
In your code.The same YAML to TSV conversion through the API, for your app or your agent.
$ cv convert report.yaml report.tsv$ cv convert report.yaml report.tsvQuestions.What people ask about YAML to TSV.
Nested objects and lists are written into their cell as JSON text. The row keeps one cell per key.
No. Comments are dropped.
No. Values such as yes, on, 0755 and dates stay text.
It is kept as an ordinary key instead of being merged into the object.