google/trillian-examples

Use YAML for human-written config files

AlCutter opened this issue · 1 comments

JSON is a reasonable compromise for machine-generated-but-human-inspectable stuff, but it's not brilliant for human-authored configs. YAML is much better at this, and in theory at least, is a super-set of JSON so perhaps any existing JSON configs will continue to work.

The remaining json files aren't configs that we are in control of, or are for human configuration:

./witness/ethereum/package.json
./feeder/ethereum/package.json
./binary_transparency/firmware/testdata/firmware_metadata.json
./binary_transparency/firmware/testdata/firmware_statement.json
./.github/workflows/link_checker_config.json

Well done team, we got 'em all!