Sniffing CSV dialect: an option not the default?

frictionlessdata / frictionless-js

A lightweight, standardized library accessing files and datasets, especially tabular ones (CSV, Excel).

https://frictionlessdata.io

71 stars 8 forks source link

Sniffing CSV dialect: an option not the default? #52

Open rufuspollock opened 5 years ago

rufuspollock commented 5 years ago

Atm we auto-sniff the CSV dialect if it is not provided. This adds complexity (and overhead) to use.

Maybe we could switch to being an option rather than the default.

@anuveyatsu any idea why we started doing this?

anuveyatsu commented 5 years ago

@rufuspollock we started doing this to support different field delimiters such as semicolon etc.

rufuspollock commented 5 years ago

@anuveyatsu makes sense. Do you think it should be optional or not?

anuveyatsu commented 5 years ago

@rufuspollock I might be wrong but as I know in some countries, e.g., France and Italy ; is used more frequently than , as a field delimiter. I've also seen some sources with tab delimited fields. However, I'm not sure how often they are. I think we should keep it as default right now and wait for an issue from users.