Comments (4)
It's been a minute since I made any changes to the GitHub Workflows schema, but I thought I had been careful about not doing anything like this because it would fail... 😿
I'm marking this as an upstream schema issue and I'll look at what's up with the GitHub Workflows schema.
from check-jsonschema.
I think I know how to adjust the schema for this. I'm going to try to put together a PR.
Regarding the error printing: you might prefer the --verbose
output, which prints all errors, not just the "best match".
I often find that the "best match" error found by jsonschema
over a oneOf or anyOf is not the most informative one, but when I try to tinker with that behavior I can't find a better way of doing things. It always fails for some cases.
from check-jsonschema.
awesome! thanks for the quick response and effective fix ❤️
from check-jsonschema.
With the upstream PR merged, I released v0.16.1 which vendors the new schema version. I checked that it passes on the example workflow above, so I'm going to mark as closed.
I see the downstream PR where you hit this issue is already merged, so it's a little late. Even so please let me know if you see any issues with check-jsonschema
.
Thanks for the issue report!
from check-jsonschema.
Related Issues (20)
- Validating a deeply nested schema using custom "strict" draft 2020 metaschema can be very slow HOT 3
- --verbose doesn't seem to be anymore verbose than without it HOT 3
- Validation fails when expression is used in `matrix.include` HOT 4
- Support loading of GitLab `!reference` data during validation HOT 1
- OverflowError: mktime argument out of range HOT 12
- Update to use the `referencing` implementation of ref resolution from `jsonschema` HOT 1
- Ref resolve failure when using custom metaschema HOT 13
- FailedDownloadError HOT 4
- Version 0.24.0 Failure resolving $ref within schema HOT 7
- Make the default regex mode use `regress` for JS-flavor regex format validation HOT 4
- GitLab CI yaml vaiarbles failing HOT 7
- Feature request: Allow validation of $schema specified in JSON file HOT 6
- version 0.26.1 is failing
- Output of all validated files if verbose: true HOT 4
- Bug with field named 'type' definition in '$defs' HOT 2
- Scipt hanging with json input not complying with schema HOT 2
- Support verbose output in pre-commit hook HOT 2
- Q: equivalent to old CLI syntax? HOT 3
- Warn when using schema features annotated with `"deprecated": true` HOT 3
- Support for `default.json` for `renovate` HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from check-jsonschema.