JSON Schema should be valid JSON

[mvahowe]

The schema on the develop branch fails because of a trailing comma in one of the files, see screenshot.

@jonathanrobie @joelthe1 Is this because you are rolling your own personal version of JSON? If not, could we try following one of the most well-established standards in the history of computing?

[mvahowe]

Here's where that comma was introduced (by me, 6 years ago).

The comma became a trailing comma when @jtauber removed other items in November 2021, shortly after he took over maintaining the schema from me. So it has been broken for 5 years.

[imnasnainaec]

@mvahowe The file from your first screenshot is orphaned and slotted for removal: #348

[mvahowe]

@mvahowe The file from your first screenshot is orphaned and slotted for removal: #348

But right now it breaks most documentation tools. It's a one-character edit. You've spent more time (or tokens if you're a bot) writing that comment than you'd need to fix the issue.

There's a tool called git that has a concept called commits which enables one to change sets of files in an ordered way. Maybe that could help?