support conversion to LocalDateTime (you need to specify the expected format).

because german uses a comma instead of a dot for floats, their csv often uses a semicolon instead)

while the separator in csv is often a comma and the quote a double quote, it's a good idea to make that configurable (e.g.

you don't seem to support nullable types currently, it makes sense to map empty strings in the csv to null, if the type you map to is nullable.

column names and values might be surrounded by quotes so that they can contain a comma (so your line splitting has to be a bit smarter than simply splitting by comma ).

column names (the comma-separated elements of the header) might contain spaces, so while the property name is a good default, you might want to add an annotation that let's you define a different name (e.g.

I called my project KSV.ĬSV contain some interesting corner cases that you might want to consider: I recently wrote a csv to Kotlin data class parser for my work at 'Which?' as well 😅. It is already available at Maven Central for download.Ĭool, csv-parsing is a nice, self-contained but useful problem domain! Let's get back to my Kotlin-Grass, a CSV to data class parser. Since this one is implemented in Kotlin Multiplatform I don't intend to reinvent the wheel for reading CSV File. It requires another awesome Kotlin library for reading the CSV, namely Kotlin-CSV. Unlike some existing Java CSV parsers, it doesn't require to invade your data class with annotation to map CSV file columns to data class fields.

So I decided to create one, and it is now available on GitHub Kotlin-Grass. To this date, I haven't found one unique implementation on Kotlin CSV parser into Kotlin data class. Hopefully one day the API version Lint checks will work on Kotlin code, since it would've caught this problem.4. What's wrong with the following code (when used on Android)? val map = mapOf('hello' to 'goodbye')

Kotlin mapof