Whitespace after delimiter can result in read error about csvhelper

[akamor]

And also, in case we dont talk again let me say thanks a lot for your support of csv helper. were huge fans.

[JoshClose]

That's not a valid CSV file.

You can handle this by setting the trim option TrimOptions = TrimOptions.Trim

[akamor]

Got it. I suspected that was the situation but thanks for confirming.

I've noticed that Excel seems to almost always open CSVs (even invalid ones). For whatever reason, it is just very relaxed in the set of inputs it can accept. Is there any documentation on the collection of config options we should employ via your SDK to essentially accept even malformed csvs, or said another way how can we replicate excel's behavior?

[JoshClose]

There is no set of things. Typically, you want to know when things aren't working as expected.

Setting TrimOptions = TrimOptions.Trim | TrimOptions.InsideQuotes should be pretty safe. You can set what is trimmed via the WhiteSpaceChars setting. By default it's just a space character.

You can change the behavior of BadDataFound to just ignore the issue with BadDataFound = null, but depending on the reason, it could mess up the rest of the read. You might want to log when this happens or something.