check-jsonschema
check-jsonschema copied to clipboard
A CLI and set of pre-commit hooks for jsonschema validation with built-in support for GitHub Workflows, Renovate, Azure Pipelines, and more!
Hi The following is not working ` check-jsonschema --schemafile 'https://www.bluetooth.com/specifications/specs/mesh-cdb-1-0-1-schema.json#' example.json Error: Unexpected Error building schema validator FailedDownloadError: got responses with status=403, retries exhausted` While the following is working (notice...
> **New in draft 2019-09** The `deprecated` keyword is a boolean that indicates that the instance value the keyword applies to should not be used and may be removed in...
As of now you get parse errors for common modern/human-readable JSON config usage - trailing commas, comments, etc. Changing extension of some of these files is impossible because they belong...
For context, see: https://github.com/go-task/task/pull/1476#issue-2088860506 For potential users who are not Python users, it's harder to use the CLI because they need to learn how to setup an environment (pipx, etc)....
Is there any interest in adding support for checking yaml files with multiple documents in them? That is: `catalog-info.yaml:` ```yaml --- apiVersion: backstage.io/v1alpha1 kind: System metadata: name: example-system spec: owner:...
As title says, e.g.: ``` # yaml-language-server: $schema=https://raw.githubusercontent.com/compose-spec/compose-spec/master/schema/compose-spec.json ``` Pretty sure that's the most common way of describing schemas in YAML as of today. Would be nice to support it.
Instead of duplicating everything here is my problem. If you want me to copy anything for this issue I can. https://github.com/awslabs/amazon-ecs-intellisense-schema/pull/8 I am looking to see how I can support...
Please consider adding line numbers to the output when schema validation errors are detected. It would be much easier to locate errors when running as a pre-commit hook, especially in...
Heyho, I have created a generic schema that I want to run against json files in different projects. This works great by passing in a schemafile to the validator. But...
## Preface GitLab `!reference` support was added in https://github.com/python-jsonschema/check-jsonschema/issues/112 but there are still some edge cases. ## How I verified that there are no duplicate issues in the issue tracker...