search

microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
183 stars 82 forks source link

Export CSV feature doesn't work correctly #126

Open chrisdolby-HE opened 3 years ago

chrisdolby-HE commented 3 years ago

Hi there,

I would have thought that this issue has come up before, but exports from the Retrospectives extension are in plain UTF-8 with only simple comma separation and no containing delimiters for, you know, sentences.

Please could someone look at adding in more cleanly exportable options, even Excel if need be? CSVW is also an option but probably a lot of extra weight and complexity.

aryyh commented 3 years ago

Yes, came across this today too. Comma's in sentences break the exported CSV

cujo-msft commented 3 years ago

Same issue here, can you advise when this will be worked?

rwhitworth127 commented 3 years ago

Same, I originally brought up the idea of having an export to csv feature. The work happened fairly quickly, but I saw the same problem, commas in sentences break the export. I am not sure what the easiest path forward is here, but fixing csv, changing to tab formatted, or Excel (xlsx) would be great.

kaskadz commented 3 years ago

I'd like to bump up this issue. The RFC 4180 (section 2.6) states:

Fields containing line breaks (CRLF), double quotes, and commas should be enclosed in double-quotes. For example:

   "aaa","b CRLF
   bb","ccc" CRLF
   zzz,yyy,xxx

I believe this guidance should be followed. Additionally some escaping mechanism should be introduced. The same RFC in section 2.7 states:

If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote. For example:

   "aaa","b""bb","ccc"

Are there any plans to tackle that issue?

mindlessroman commented 2 years ago

@kaskadz - I believe this was handled in a recent release. Can you confirm?