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
The schema suggests that all id fields should start with the value of the origin field, followed by a colon :, but nothing actually validates that. It would be a good step towards protecting the integrity of the data to actually validate that it does, either via JSON schema in kcidb-io (if possible), or by other means in kcidb.
The text was updated successfully, but these errors were encountered:
Sorry, @NikkyXO, we still have to figure out how exactly to do this. We have some inherited data (v3 upgraded to v4) that violates the rule we're trying to introduce, and need to figure out how to resolve that.
The schema suggests that all
id
fields should start with the value of theorigin
field, followed by a colon:
, but nothing actually validates that. It would be a good step towards protecting the integrity of the data to actually validate that it does, either via JSON schema in kcidb-io (if possible), or by other means in kcidb.The text was updated successfully, but these errors were encountered: