JSON Validator doesn't catch extra commas

Issue Description: The json validator and schema provided in the documentation does not catch unnecessary trailing commas. The json is legal but it will not be accepted by the OW dev console.
Steps to reproduce:

  1. download the sample app
  2. inspect the manifest
  3. add a comma to the last field in array or object:
    Ex:
    “extra-objects”: {
    “simple-io-plugin”: {
    “file”: “simple-io-plugin.dll”,
    “class”: “overwolf.plugins.SimpleIOPlugin”
    }
    },
    would become:
    “extra-objects”: {
    “simple-io-plugin”: {
    “file”: “simple-io-plugin.dll”,
    “class”: “overwolf.plugins.SimpleIOPlugin”,
    }
    },

The validator will accept both objects but the latter will be rejected by the dev console.

Impact for my app: low-mid. This issue slows down the process to get a new app on the store. With out access to the dev console the time to fix is even longer.

Do you currently have a workaround?

The only workaround right now is to manually inspect the manifest for any incorrect commas.

@bmills95 I guess that the right solution will be to fix the JSON validator and schema provided in the documentation, so it will also reject files with extra commas.

I will check if and how it’s possible.

Thanks.

@bmills95 I couldn’t find a way to add extra commas validation to our schema validator. It’s more a JSON structure issue. So I updated our docs accordingly:

Thanks for raising the issue. With your permission, I will close the ticket now.

Excellent. Thank you for updating the docs. We can close this.