Feature: Describe how .csv should look like about hammond HOT 5 OPEN

@AlfHou I’d suggest using the structs for the fillups and expenses from the go app.

I’m also working on a generic import functionality. Allowing the user to select which field corresponds with the fillup/exspense struct.

from hammond.

Sorry for the late reply. Easter and all that.

So what you would like to see is some kind of CSV specification for generic imports? I think that should definately be doable. Might just reuse fuelly's format or something. I'll look into it

from hammond.

This is still needed.

It’s unclear what format the generic csv importer needs for its fields, e.g. datetime-format, decimal point comma or dot, quotes around numbers, leading zeroes and int vs float values (42.0 vs 42)

from hammond.

@vKnmnn hope this helps for now.

Any value that has a decimal must be a delimited by a dot
Datetime is any format that javascript can use to create a date using new Date()
Numbers do not need a leading zero and it doesn't matter if they're quoted or not

from hammond.

Thank you @alienp4nda. We might want to add a description for this in the importer itself. I'll try to add this during the weekend.

from hammond.