Closed Msgtfrank closed 7 years ago
I think we should put some level of validation to those packages. We could use jsonlint, and if we have well defined schema (i.e. every json must have the "Library" ) we can code an automated test to validate that for each of them.
I did a little script to run jsonlint over the json files, and only one of them has an invalid schema, but it is not related to this PR. All the files @Msgtfrank is uploading are correct for jsonlint. For reference, this is the broken file:
+ jsonlint src/ads1x15/ads1x15.json --quiet --compact
src/ads1x15/ads1x15.json: line 39, col 18, found: '}' - expected: 'STRING'.
"Platforms":
{
"Intel Joule Module":
{
"Notes": ["On SeeedStudio Grove Shield for Intel Joule"]
},
"Intel Edison Module":
{
"Notes": ["On SparkFun Block for Intel Edison - ADC"]
}, <<<<<<<<<< INVALID COMA CHARACTER HERE
},
Added this first cluster of 40 JSON files