They're valid. It's giving those errors on any JSON file I've tried (all from pa/units), such as assault_bot.json. Only one I found that worked was radar_adv.json. Will give it another go later. EDIT: Just tried again and it seems to be working. Not sure if it was due the folder I was trying to edit them in (AppData, Program x86, etc) or because I needed to restart or whatever. Seems to be working just fine though now!~
Is anyone interested in a pretty printing json parser that has slightly better error reporting? Points to the problematic area with a handy source preview. Warns about numbers or extra commas (but tries to parse it anyway). Finally, you can include comments! Keep in mind that PA does not support comments, so you really should strip them out (the script can do that).
I've just started trying out Microsoft Visual Code which will identify issues as you edit the files. Something which spots them prior to saving is probably better than something which can notify you after. Sublime Text does the same I believe.
Does the Microsoft product do it for json too? If so, pretty nifty. My use case for this parser though is to integrate with some of my other tools. Also, I was bored .
I spent more time trying to set it up to work with Git than I did using it, but it looked like it did. Certainly it was highlighting (and its highlighting default is better than Notepad++'s), and it noticed a missing comma immediately. Will be playing around with it more tonight.
Just to confirm, it will detect errors in JSON in real time. Visual Studio Code is also open source, if that's important to you.
I just checked it out, it's really amazing. Looks like Microsoft is going to have a monopoly on programming software again.