Last modified: 2014-03-31 08:19:46 UTC
In Gerrit change #122270, a line in JSON contained the following: "key" => "value", The Jenkins jobs for the Scribunto extension, and in particular the job jslint I believe, didn't disapprove of this, even though it is invalid JSON. https://integration.wikimedia.org/ci/job/mwext-Scribunto-jslint/598/console is the job output. Expected behaviour: JSON linter should catch JSON syntax errors and jobs running this linter should fail in such cases. I set the severity for this issue to major.
For comparison: $ json_verify < i18n/qqq.json lexical error: invalid char in json text. { "@metadata": { " (right here) ------^ JSON is invalid
Json files are not validated yet. Need to add to the jslint jobs the json_decode() wrapper I wrote which is bug 58279. I forgot to deploy it last week. *** This bug has been marked as a duplicate of bug 58279 ***