You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously in #78 I deprecated --flatten for usage consistency. But I recognized it complicates life with more structured files.
For example, xlsx workbook contains worksheets, which constructed from rows, each of which is an array of columns. Emitting a workbook as a single JSON array is correct, but post-processing of such JSON usually requires complex jq filtering. It is quite time-consuming.
Instead, if such a workbook is emitted as row-by-row ndjson, we can easily spot interesting items with grep and/or less. And you can still use jq for it too.
One idea to solve above is introducing --output_filter=flatten and allow users to implement their own filters.
The text was updated successfully, but these errors were encountered:
Previously in #78 I deprecated
--flatten
for usage consistency. But I recognized it complicates life with more structured files.For example,
xlsx
workbook contains worksheets, which constructed from rows, each of which is an array of columns. Emitting a workbook as a single JSON array is correct, but post-processing of such JSON usually requires complex jq filtering. It is quite time-consuming.Instead, if such a workbook is emitted as row-by-row ndjson, we can easily spot interesting items with grep and/or less. And you can still use jq for it too.
One idea to solve above is introducing
--output_filter=flatten
and allow users to implement their own filters.The text was updated successfully, but these errors were encountered: