bug: CSV Data Corruption

[akramcodez]

Description

The custom parseCSVLine logic incorrectly toggles the inQuotes state without handling quotes or escaped characters. Inputs like "foo""bar" are parsed incorrectly.

// Input
'"foo""bar",baz'

// Output
['foobar', 'baz']

// Expected
['foo"bar', 'baz']

Impact

• Silent data corruption for fields containing quotes
• Downstream analysis failures with standard CSVs
• Loss of data integrity in exported reports

Potential Fix

Rewrite the parser to handle escaped quotes ("") or replace it with a standard library like csv-parse.

[AnanthuNarashimman]

Hi, I would like to work on this issue. I plan to investigate the parseCSVLine logic and modify it to correctly look ahead for escaped quotes (double double-quotes) per CSV standards.

I will also add a unit test to cover the foo""bar case to prevent regressions. Could you please assign this to me?