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
I'm opening this Issue as a way for me to ask the SchemaStore project a single question: is there any interest in also providing the fab corpus of schemas that the project currently serves as JSONSchema, but as CUE's .cue files?
With (IMHO!) fantastic foresight, SchemaStore has established the canonical source of JSONSchema docs via a json-specific FQDN (json.schemastore.org). CUE has the concept of importing externally-defined CUE config repositories, and is working on designing and implementing the automated fetching of those external sources. I figured I'd ask SchemaStore's folks if there's any interest in investigating the value of being the canonical source of directly-importable CUE schemas for folks in that tooling ecosystem? Perhaps (and this is a really early, unbaked idea!) as something like cue.schemastore.org?
I've done some initial work on how one could process SchemaStore's existing .json corpus, in a fork over here: https://github.com/cueniform/schemastore/tree/cueniform_main. Before I do much more in that fork, I thought it'd be a good idea to reach out and ask for your feelings on this. Of course, there's absolutely no worries either way - a "no thanks, our focus is solely on JSONSchema documents" is as useful as a "yes!", as it gives me just as much a direction to move :-)
Whatever response this gets - thanks a million for this fantastically useful project :-D
[PS I have nothing to do with the CUE project - I'm simply a happy and appreciative user of both SchemaStore and CUE!]
Are you making a PR for this?
Yes, I will create a PR.
The text was updated successfully, but these errors were encountered:
As @GerryFerdinandus mentioned, this site focuses on JSON Schemas that can then be used by any language server that supports them, such as JSON, YAML, TOML, etc. If CUE's editor implementation could be made to support JSON Schemas, then it can interface directly with the API available here on SchemaStore.org.
Description of the feature / enhancement.
Hello! 👋
I'm opening this Issue as a way for me to ask the SchemaStore project a single question: is there any interest in also providing the fab corpus of schemas that the project currently serves as JSONSchema, but as CUE's .cue files?
With (IMHO!) fantastic foresight, SchemaStore has established the canonical source of JSONSchema docs via a json-specific FQDN (json.schemastore.org). CUE has the concept of importing externally-defined CUE config repositories, and is working on designing and implementing the automated fetching of those external sources. I figured I'd ask SchemaStore's folks if there's any interest in investigating the value of being the canonical source of directly-importable CUE schemas for folks in that tooling ecosystem? Perhaps (and this is a really early, unbaked idea!) as something like
cue.schemastore.org
?I've done some initial work on how one could process SchemaStore's existing .json corpus, in a fork over here: https://github.com/cueniform/schemastore/tree/cueniform_main. Before I do much more in that fork, I thought it'd be a good idea to reach out and ask for your feelings on this. Of course, there's absolutely no worries either way - a "no thanks, our focus is solely on JSONSchema documents" is as useful as a "yes!", as it gives me just as much a direction to move :-)
Whatever response this gets - thanks a million for this fantastically useful project :-D
[PS I have nothing to do with the CUE project - I'm simply a happy and appreciative user of both SchemaStore and CUE!]
Are you making a PR for this?
Yes, I will create a PR.
The text was updated successfully, but these errors were encountered: