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
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
In the data.json validator (at least the version where you paste in JSON), bad fields bring up helpful error messages, along with links to the metadata schema. As near as I can tell, those schema links don't change based on which schema version you're validating against. It would be nice if the error page changed the schema links to correspond to the version the user is validating against. So when checking for 1.0 compliance, the link would go here, whereas when checking for 1.1 compliance, the link would go here.
The text was updated successfully, but these errors were encountered:
In the data.json validator (at least the version where you paste in JSON), bad fields bring up helpful error messages, along with links to the metadata schema. As near as I can tell, those schema links don't change based on which schema version you're validating against. It would be nice if the error page changed the schema links to correspond to the version the user is validating against. So when checking for 1.0 compliance, the link would go here, whereas when checking for 1.1 compliance, the link would go here.
The text was updated successfully, but these errors were encountered: