Open kevin-montrose opened 4 years ago
Pretty sure our codebase outputs a file using double-pipes ||
as a delimeter for a third-party report. So we sometimes need more than one character as a delimeter.
@fjmorel iiiinteresting - the thought had crossed my mind but I couldn't dig up a concrete example. Is it possible for you to share more details (like, the subject matter or third party, really anything to contribute to grounding the use case)?
Hmm, I could have sworn we had something like this, but am not finding it anymore.
We definitely have #*#
though, in some reports generated for a music label.
writer.WriteLine(string.Join("#*#", arrayOfValuesWeDidNotEscape));
btw, the Overthinking CSV With Cesil: CSV Isn’t A Thing
link goes nowhere. Same for the first post of this series link.
Ah, thanks for pointing that out - I've fixed the links in the issue.
That's a pretty concrete example, a second thanks for sharing it. I'll proof out making Options.ValueSeparator
a string in a branch - the write side should be simple, the read side might take a bit...
The full change is ready in #12 now.
This was posed in Overthinking CSV With Cesil: CSV Isn’t A Thing.
Essentially, are the configurations exposed via
Options
adequate?This was restated as:
in Overthinking CSV With Cesil: “Maximum” Flexibility
This is an Open Question, which means: