You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: