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
Thank's for the great library. I use it in some of my projects and very happy with results (especially combined with Mosaic).
In one of my projects I've faced with requirement to output data as CSV along with human-readable tables. I've came up with my
own solution (not a rocket science) and got thinking that there could be some CSV related API in Picnic.
CSV (or more general DSV) format has no different in meaning from ASCII tables
Such new rendering API could benefit from existing Mosaic API (rows, columns, cell, columnSpan)
On the other side new API could contradict the single responsibility principle of the library (only ASCII tables)
So my questions are:
what do you think about supporting CSV?
if it works will you add that API in some future?
may I help with this?
Thank you
The text was updated successfully, but these errors were encountered:
I don't think it makes sense to include directly, but rather as a companion library. I personally don't use CSV or DSV and don't feel qualified to maintain such a thing. I made the mistake in my last table library of adding support for ResultSet conversion for databases, and regretted it more than once.
Thank's for the great library. I use it in some of my projects and very happy with results (especially combined with Mosaic).
In one of my projects I've faced with requirement to output data as CSV along with human-readable tables. I've came up with my
own solution (not a rocket science) and got thinking that there could be some CSV related API in Picnic.
So my questions are:
Thank you
The text was updated successfully, but these errors were encountered: