[x3d-public] Low hanging fruit for JSON parsing (not validation) of archive.

[John Carlson]

Indeed, it looks like at least one of these files was updated in April.  
Ignore the below message, I will produce an alternative result.

John

On 3/30/21 5:48 PM, John Carlson wrote:
> Low hanging fruit for JSON parsing (not schema validation) $ grep 
> Failed results.txt|grep -v node_modules
> Failed JSON parse 
> /c/x3d-code/www.web3d.org/x3d/content/examples/Savage/Scenarios/LimitedObjectiveExperimentPortHueneme/LimitedObjectiveExperimentPortHuenemeDIS.json 
> SyntaxError: Unexpected string in JSON at position 11316
> Failed JSON parse 
> /c/x3d-code/www.web3d.org/x3d/content/examples/Savage/Scenarios/LimitedObjectiveExperimentPortHueneme/LimitedObjectiveExperimentPortHueneme.json 
> SyntaxError: Unexpected string in JSON at position 10445
> Failed JSON parse 
> /c/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/PanamaCityFlorida/PanamaCityGeo.json 
> SyntaxError: Unexpected string in JSON at position 5198
> Failed JSON parse 
> /c/x3d-code/www.web3d.org/x3d/content/examples/Savage/Weapons/UnderwaterMines/SphericalMinePrototype.json 
> SyntaxError: Unexpected string in JSON at position 23534
>
>
> These are things jsonlint should catch.   I am not sure about jshint 
> or jslint.
>
>
> These files are dated Jan 23 2021. Your files may be more up to date 
> as I don't really know how to update Savage svn.
>
>
> I am currently wondering if JSON files are checked into Savage folder 
> or not.  I will re-expand my JSON zip and try again.
>
>
> John
>
>
>