Repository navigation
Conversation
|
Hi @Yakwilik! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2514 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 31 31
Lines 695 695
Branches 215 215
=========================================
Hits 695 695 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Updated the tooling entry in 04f45bf to use the supported homepage field instead of the reserved documentation field. Validate Tooling Data and PR body validation now pass. The remaining Build Preview Deployment failure is unrelated to this tooling entry: the build fails while prerendering /community because the community iCal URL returns 404. This is already tracked in #2506 and is reproducible on other PRs as well. |
What kind of change does this PR introduce?
Feature / tooling catalog update.
Issue Number:
Screenshots/videos:
Not applicable — this change adds a tooling catalog entry only.
If relevant, did you update the documentation?
Yes. The tooling catalog entry itself is the documentation update.
Summary
Adds
go-yamlvalidatorto the JSON Schema tooling catalog as a Go validator that applies JSON Schema to YAML while preserving YAML source locations in diagnostics.The entry explicitly declares its dependency on
https://github.com/santhosh-tekuri/jsonschemathroughdependsOnValidators, since go-yamlvalidator is an adapter/source-mapping layer rather than a separate JSON Schema engine.Supported dialects: draft-04, draft-06, draft-07, 2019-09, and 2020-12.
The public JSON Schema adapter is covered against the official JSON-Schema-Test-Suite in CI across the supported drafts.
Does this PR introduce a breaking change?
No.
Checklist