SchemaStore / SchemaStore/schemastore

VSCode and Non Compliant Schemas Needed for Compatibiity

Open
#5,657 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Question
Dominant language
JavaScript
Stars
3.8k
Forks
2.3k
Avg merge
20h 23m
Merged PRs (30d)
124

Description

Description of the JSON schema.

Hello I hope all is well. I wasn't really seeing a place to ask a question. I can close this and ask it somewhere else if you can supply me where that should be. But here is the question.

Our team is developing a json schema that is bundled from other schemas. We are using the red hat YAML Extension to get intellisense for our YAML files via the schema.

We are using source meta's bundler (https://github.com/sourcemeta/jsonschema/blob/main/docs/bundle.markdown) which mentions that VSCode supports a non compliant version of the schemas. As such I was wondering how that would work with posting our schema to the schema store? Should we post up two version? One non compliant bundled version dedicated for VSCode and one that is a compliant version for other uses? Any idea how the Red Hat YAML Extension would work with two versions out here in the Schema Store?

Supporting information.

NA

Are you making a PR for this?

No, someone else must create the PR.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or implementation entry point is named. First clarify how Schema Store should handle bundled non-compliant schemas and how the Red Hat YAML Extension selects between versions; done would be a documented answer directing the reporter to the appropriate process or support channel.

Written by the indexing model from the issue text.

Assessment

Tech stack
json, vscode, yaml
Domain
documentation, tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.