Input musn't be finnicky
Column names with "
in the name, a row with fewer columns than the rest, strange line endings, trailing tabs, consecutive tabs, UTF16-LE BOM encoding, dos line endings. All these weird cases should either be supported or yield an error which tells the user exactly what's wrong and how to fix it. Plus it shouldn't look like a traceback, users don't read those because that's not how you show errors to users, that's just for devs.
So:
-
Handle various encodings -
Handle strange line endings -
Whitespace is insignificant, i.e. it can't break things -
User friendly error messages for common input errors
Edited by Tim Diels