Use schema to validate document.commit in knowledge is a 40 char hexadecimal SHA value

[bjhargrave]

In the taxonomy repo, there is discussion about further validation of the document information in a knowledge contribution. One thing the schema can do is validate that the document.commit value is a 40 char hexadecimal SHA value.

See https://json-schema.org/understanding-json-schema/reference/string#regexp

[bjhargrave]

We could required the commit value to always be 40 chars. This would be an issue for some existing knowledge documents.

{  
  "type": "string",
  "pattern": "^[a-fA-F0-9]{40}$"
}

Or we could allow it to be between 7 and 40 chars. This should validate any existing knowledge documents.

{  
  "type": "string",
  "pattern": "^[a-fA-F0-9]{7,40}$"
}

[bjhargrave]

My latest thinking is that we do not want to do this detailed validation. I think at some point we will need to allow the knowledge markdown to live in the taxonomy repo alongside the qna.yaml. Then we will need a "special" commit value to indicate the knowledge is in the same commit as its peer qna.yaml.