Support CSV for recipients

[gbonnefille]

CSV is a classical input format.

Fixes #1

[rykov]

CSV is classic. I would inline newCSVReader and unmarshalYamlRecipients because they are quite short and used only once.

[rykov]

@gbonnefille Thinking further about this in the context of what I commented on #40, what do you think about moving CSVConfig into the CSV frontmatter? Seems like a better place for it than the global configuration.

[gbonnefille]

CSV is classic. I would inline newCSVReader and unmarshalYamlRecipients because they are quite short and used only once.

I have no opinion on such improvment. Feel free to apply any change you consider.

[gbonnefille]

@gbonnefille Thinking further about this in the context of what I commented on #40, what do you think about moving CSVConfig into the CSV frontmatter? Seems like a better place for it than the global configuration.

I'm not sure to understand: you want to set the set the Comma property in a comment of the CSV file?

Of course, it seems a good idea as it is clearly coupled with this file.

Nevertheless, as it is a non standard feature, any user will have to edit the (generated) CSV before using it, each time it is regenerated. IMHO, a CSV file is certainly generated from another tool. Having to edit a frontmatter will break a smooth pipeline.

[rykov]

Integrated in 74c8851