Describe the bug
The CSV file created with the Export CSV button when viewing the "Checker statistics" page is not usable on Windows (e.g., as a data-source to Excel), as the file does not contain the appropriate newlines.
I get a CSV that is usable. If not appropriately aligned with Windows-specific \r\ns, then at least the \ns should be there so I can fix up the file later manually. Currently, the first column cell of the second row is immediately appended to the last column header in the first row, so it takes a lot of manual clicking back and forth to fix it.
Desktop (please complete the following information)
OS: Microsoft Windows 10 Version 22H2 (OS Build 19045.3570)
@cservakt I vaguely recall you touching things around these parts for the checker status overview pane #4210. Could you please re-check if this thing was fixed by that?
Describe the bug The CSV file created with the
Export CSV
button when viewing the "Checker statistics" page is not usable on Windows (e.g., as a data-source to Excel), as the file does not contain the appropriate newlines.See this example file:
codechecker_checker_statistics.csv
CodeChecker version 6.22 release
To Reproduce
Expected behaviour
I get a CSV that is usable. If not appropriately aligned with Windows-specific
\r\n
s, then at least the\n
s should be there so I can fix up the file later manually. Currently, the first column cell of the second row is immediately appended to the last column header in the first row, so it takes a lot of manual clicking back and forth to fix it.Desktop (please complete the following information)