{"action":"opened","issue":{"url":"https://api.github.com/repos/mdn/data/issues/19","repository_url":"https://api.github.com/repos/mdn/data","labels_url":"https://api.github.com/repos/mdn/data/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/mdn/data/issues/19/comments","events_url":"https://api.github.com/repos/mdn/data/issues/19/events","html_url":"https://github.com/mdn/data/issues/19","id":187398731,"number":19,"title":"Add schema files for validation purposes","user":{"login":"a2sheppy","id":1641439,"avatar_url":"https://avatars.githubusercontent.com/u/1641439?v=3","gravatar_id":"","url":"https://api.github.com/users/a2sheppy","html_url":"https://github.com/a2sheppy","followers_url":"https://api.github.com/users/a2sheppy/followers","following_url":"https://api.github.com/users/a2sheppy/following{/other_user}","gists_url":"https://api.github.com/users/a2sheppy/gists{/gist_id}","starred_url":"https://api.github.com/users/a2sheppy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/a2sheppy/subscriptions","organizations_url":"https://api.github.com/users/a2sheppy/orgs","repos_url":"https://api.github.com/users/a2sheppy/repos","events_url":"https://api.github.com/users/a2sheppy/events{/privacy}","received_events_url":"https://api.github.com/users/a2sheppy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-04T17:54:06Z","updated_at":"2016-11-04T17:54:06Z","closed_at":null,"body":"As part of our testing and validation before committing changes to the data, we should be using a tool such as [ajv](https://www.npmjs.com/package/ajv) to not only validate that our JSON is structurally sound, but that it matches the schemas for each of the databases we have here.\r\n\r\nThis would go a long way toward helping to ensure that our data is properly formatted and will reduce the back-and-forth during the PR process."}}
{"actor":{"display_login":"a2sheppy"}}