Handle escaping DELIMITER.FIELD about json-2-csv

[mrodrig]

By escaped, you mean adding a '' in front of the delimiter right? It's something I hadn't considered yet - I just figured that the delimiter would be changed, but if someone doesn't want to change the delimiter it is a nice feature. I'll definitely take a look at implementing this.

[pgilad]

Perhaps this could be of help, they quote elements that contain the delimiter:
https://github.com/mholt/PapaParse/blob/master/papaparse.js#L241-L389

[dillten]

@pgilad are you saying the source data looks like:

{ "key,field": "value,field" }

and you're thinking it should parse to "key,field","value,field"?

Can you provide a test case?

[pgilad]

let's assume that you have a value that holds a description or note of some kind, it might be:

//...
{ description: "Clicking this you will activate Panyo, which is a very long commented text..." }
//...

This fails if it will not be quoted. Same goes for keys

thinking again I might be wrong, since you are parsing JSON the keys/values must be quoted, so it depends if the CSV always outputs quoted elements

[dillten]

If the delimiter.field (comma) is included in a json input string and no options are specified, then yes, the output string will be incorrect. The fix would be to specify a delimiter.wrap option (typically \") to wrap all the output strings, or alternatively change the output delimiter (perhaps tab or semicolon).

I added a test to cover this condition in the wrapped output, but not sure how one would want to handle scanning a document for a conflict of this type (document contains strings that match field character with no wrap option specified) ahead of conversion.

[mrodrig]

Thanks for adding the test. The standard seems to be adding the wrap delimiter as @dillten mentioned.