There is nothing in the JSON spec that prohibits pre/post non-json parsing search / replace 'end of line' marker with one or more commas.
JSON spec just tells one what the JSON parser expects, not what the end user needs/wants. (GPT-JSON not withstanding)
There is nothing in the JSON spec that prohibits pre/post non-json parsing search / replace 'end of line' marker with one or more commas.
JSON spec just tells one what the JSON parser expects, not what the end user needs/wants. (GPT-JSON not withstanding)