Closed oliverpool closed 1 month ago
Actually, I am wondering if we shouldn't let the comma as-is (i.e. no escaping / no unescaping): the application should interpret them how they like (and this lib should make it easy to escape them)
Superseded by #35
Continuing the work started by @GorthMohogany in #11 to address #5
When decoding, it splits the value if it contains unescaped
,
From the original PR I dropped the space removal (
strings.TrimSpace(value)
) since I couldn't find anything in the RFC supporting this operation.Note that it raises further questions for fields containing unescaped commas, like in https://datatracker.ietf.org/doc/html/rfc6350#section-8 (however those can be addressed in a later PR)