problem-specifications
problem-specifications copied to clipboard
ci: check `metadata.toml` files
The prob-specs ci.yml workflow checks Markdown and JSON files, but not the metadata.toml files.
In the hopefully-unlikely event that a strictly invalid metadata.toml file reaches main, configlet sync would produce an error to complain about the invalid TOML when the syncing scope includes metadata.
We could check that:
- every exercise has a
metadata.tomlfile - with a valid
titlekey/value pair - with a valid
blurbkey/value pair - if the
sourcekey is present, the value is valid - if the
source_urlkey is present, the value is valid - there is no other key/value pair (it may be a typo of
sourceorsource_url, likesource-url)