Skip to content

config-schema.json: fixes to the schema #5654

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

Merged
merged 3 commits into from
Feb 11, 2025
Merged

config-schema.json: fixes to the schema #5654

merged 3 commits into from
Feb 11, 2025

Conversation

ilyagr
Copy link
Contributor

@ilyagr ilyagr commented Feb 11, 2025

Fixes #5607 in particular.

This can be thought of as a companion to @steadmon 's #5651.

@ilyagr ilyagr marked this pull request as ready for review February 11, 2025 01:07
@ilyagr ilyagr force-pushed the ig/jsonschema branch 2 times, most recently from c84391d to 3fe24e6 Compare February 11, 2025 01:18
This makes the schema a bit less smart, but there's a good chance
`taplo` could not use "propertyNames" anyway because that comes
from a newer version of the schema than `taplo` officially supports
(see the child of this commit).

Fixes #5607
"$comment" is not officially supported by draft-4, but it is in newer
drafts, and JSON schema readers are supposed to skip fields that
are not known to them.
@ilyagr ilyagr added this pull request to the merge queue Feb 11, 2025
Merged via the queue into main with commit a3647a6 Feb 11, 2025
42 checks passed
@ilyagr ilyagr deleted the ig/jsonschema branch February 11, 2025 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[jsonschema] <key> is valid under more than one of the schemas listed in the 'oneOf' keyword
2 participants