-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
schema.gsd.id Cloudflare Worker for schema $refs #177
Comments
schema.gsd.id/DOMAIN/SCHEMA-NAME.json (latest) or SCHEMA-NAME-1.2.3.json correct? so e.g. schema.gsd.id/osv.dev/osv-1.5.0.json or schema.gsd.id/gsd.id/osv-gsd-1.0.0.json |
I would be tempted to do a slightly different encoding, but that works, yes. Alternative idea: https://schema.gsd.id/DOMAIN/SCHEMA-NAME/version e.g. |
I think your way is better. So I'll do that. Also for content type we'll use: application/schema+json as per the draft spec: |
Oh I remember why I wanted to do it my way, it can just be files in a directory attached to cloudflare pages. |
Per slack discussion, could also do: https://schema.gsd.id/osv.dev/osv/latest/schema.json And do a direct file mapping. |
Ok as per discussion we went with human firendly and machine friendly layout: For humans we have the files with the version number embedded, e.g.: gsd.id/osv-gsd/schema-osv-gsd-1.0.1.json For computers we have the files in directories with the version number, e.g.: gsd.id/osv-gsd/1.0.1/schema.json The latest version of the schema is in the root directory and called schema.json, e.g.: gsd.id/osv-gsd/schema.json |
also I'm using cloudflare pages which serves the json as "application/json" (and doesn't seem to lead _headers rewrite it), to get the proper "application/schema+json" we'll need to use a cloudflare worker or something that allows control of the header. That's a future problem/ |
Allow validators to resolve even if the source returns text/plain
Transparent pull and reserve with proper content type.
The text was updated successfully, but these errors were encountered: