Further validation

[peternewman]

This extends the validation in #6 by actually validating against our schema.

[ssilverman]

Thanks for this.

[ssilverman]

Actually, @peternewman could you combine all the commits into one and force push?

[peternewman]

I could, or you could just use the Squash and Merge option, which is probably less effort all round:
https://docs.github.com/en/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-pull-request-commits

You might need to enable it first:
https://docs.github.com/en/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests

[peternewman]

Is the Squash and Merge option acceptable @ssilverman or do you want me to have a go from my end?

[ssilverman]

I'm familiar with squash merges, I just wanted to give you an opportunity to create your own commit message. If you don't want to, I'll just create a commit and give you credit in the comments.

[ssilverman]

See: #6 (comment)

[peternewman]

I'm familiar with squash merges, I just wanted to give you an opportunity to create your own commit message. If you don't want to, I'll just create a commit and give you credit in the comments.

I thought I'd replied before, but seemingly not.

It strikes me the squash within GitHub's UI is probably the best option, you get to specify the commit message, which means you can standardise them and keep them consistent between contributors, where the GitHub squash will retain my authorship of all the commits in blame etc (as opposed to just a comment in a commit message).

Otherwise if you'd like to propose a commit message, I can do the squash in another branch and open yet another PR if you really don't want to use GitHub's squash UI yourself?

"Add jsonlint GitHub Action for automatic JSON validation"?