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 JSONSchema tooling supports importing schemas referenced by their ID when that ID is a URL; which is why we've chosen to use this ID format. However, in order to make that possible, we need to actually serve the schema documents at that URL. I expect this could be done in one of two ways:
dynamic proxying of the raw content from the Github Repo
bake in the documents through the build process to be served directly
The text was updated successfully, but these errors were encountered:
Currently we are using a URL identifier for our OpenSLO Schemas in this format:
The JSONSchema tooling supports importing schemas referenced by their ID when that ID is a URL; which is why we've chosen to use this ID format. However, in order to make that possible, we need to actually serve the schema documents at that URL. I expect this could be done in one of two ways:
The text was updated successfully, but these errors were encountered: