Materials-Consortia
Add extra schema checker jobs to CI
Closes #575
I've also tweaked some of the rst roles in the spec to maybe allow us to scrape the spec for all fields (in a2cb422). It might be worth adding some special role to the headers that define fields to make this even easier, otherwise I'll concoct some grep incantation to try and do the same job without needing any changes to the spec.
This PR now has a checker for:
- building an validating existing schemas in CI
- scraping the spec for property names and checking they have schemas (to be replaced eventually when we generate the spec from the schemas themselves) -- currently failing as we await trajectories fields.
After the meeting we decided to remove the blocking-release label from this PR -- I'm wondering if instead I should merge in the "uncontroversial" part which is just calling the make schemas tool in our CI, and leave the other "checking for fields in the spec that don't have definitions" part for a future PR.
After the meeting we decided to remove the
blocking-releaselabel from this PR -- I'm wondering if instead I should merge in the "uncontroversial" part which is just calling themake schemastool in our CI, and leave the other "checking for fields in the spec that don't have definitions" part for a future PR.
Splitting off uncontroversial make schemas part sounds like a good idea to me!
