Permissive parsing of commas in human written JSON

[James Powell]

Missing commas (or an extra one at the end of a list) are very common human errors. Usually, these errors are in JSON formatted with new-lines. Adopt, on read:

• comma can be missing if there is a LF/CR
• extra comma at end of list (object/array) is ignored if it has a following LF/CR

This follows (roughly) specs like JSON5.

‌

[James Powell]

Example of missing commas:

‌

[
  1
  2
  3
]

And extra comma at end:

‌

[
  1,
  2,
  3,
]

‌

[James Powell]

200ecde1a2fa30e837c09e10683c655758026532

--> LF/CR can serve as comma

--> trailing comma in list allowed, even without LF/CR (Note: I think this was already TRUE!)

[James Powell]

Reopen. Issue with Inserting of items; adds a comma, so trailing comma becomes two commas, which is an error.

[James Powell]

Need a way to know if a trailing comma exists.

[James Powell]

I had to redo the info collected by teh Find functions, so I could determine whether or not a comma needs adding on insert, or removing on delete

[James Powell]

1.5.3