Closed callummole closed 2 years ago
I expect that there will come a moment when we'll have to go through all the issues, standardise the format, and then start imposing that standard from there on.
Proposal (see also reporting.mld
):
turing-project-code
or allow a YAML list of codes. At any rate, change the name to finance-codes
. earliest-start-date
(with the meaning "any time")latest-start-date
(with the meaning "never")latest-end-date
(with the meaning "never")max-FTE-percent
, min-FTE-percent
(with meaning "same as nominal-FTE-percent
")nominal-FTE-percent
(with meaning 100).-FTE-percent
s should be integersFTE-months
or FTE-weeks
return either (with type). I've written some notes in lib/reporting.mld
on the errors and warnings that ought to be reported. (Noting that this document is not the last word!). I will close this issue but we can open another one which is more specific: eg, "fix reporting by github.ml to match documentation" or "ensure all projects have valid metadata blocks".
In the PR #20 we separate the metadata validation to
Github.ml
. When running this code we get a lot of errors logged, e.g. a snapshot:These need inspected to see if these are genuine errors or whether the metadata parsing needs improved to catch different specifications of metadata. For example, on an initial inspection some metadata were specified with
---
instead of+++
, and they sometimes had spaces after the value entries.