@dkalinai I just released version 1.4.0 of CSVImporter with support for specifying the files string encoding. Note that your file was .utf16LittleEndian encoded (see also the spec I added here).

At first even after allowing to specify the encoding the spec was failing – the reason was, that CSVImporter relies on the structure defined by RFC 4180. In 2.4 the standard specifies the following:

Within the header and each record, there may be one or more
fields, separated by commas. Each line should contain the same
number of fields throughout the file. Spaces are considered part
of a field and should not be ignored. The last field in the
record must not be followed by a comma.

After having a look at your file I found that it didn't comply to the standard, so I removed the commas at the end of each line, then the specs were passing. I hope you can get around this restriction somehow, I don't know where your file came from, but it was not a valid CSV file as it seems.

As for Quick and Nimble: True, my fault, I forgot that I used those in this project. I'm a fan of the DRY principle which Quick helps a lot with and Nimble is so much more readable then XCTAsserts – so I think those two will be the future best practices. The testing stuff is already done for this feature but if you're interested in a better testing framework you might find this post helpful.

Uh oh!

Support CSV files with UTF16 encoding #12

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions