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
While the TSV type output is fine, if one is directly ordering from the BOM, such as through Digikey, CSV format is preferred. A simple way to do this is to switch the custom tsv generation to the CSV library, which supports both tsv and CSV, and using additional flags to determine which formats are outputted.
Additionally (and this may be best as a separate issue), the SVG output may be able to be in-lined with the HTML so that it can be an option that can be turned on and off depending on what the user wants, just like with the different BOM formats.
The text was updated successfully, but these errors were encountered:
I suggest using Tablib not only for CSV/TSV output, but to support the entire BOM handling. It can also generate the HTML table and thereby ensure consistency between the different formats.
EDIT: The function of generating BOM might depend on an additional CLI switch, as suggested in #367 (comment).
While the TSV type output is fine, if one is directly ordering from the BOM, such as through Digikey, CSV format is preferred. A simple way to do this is to switch the custom tsv generation to the CSV library, which supports both tsv and CSV, and using additional flags to determine which formats are outputted.
Additionally (and this may be best as a separate issue), the SVG output may be able to be in-lined with the HTML so that it can be an option that can be turned on and off depending on what the user wants, just like with the different BOM formats.
The text was updated successfully, but these errors were encountered: