Skip to content

feat: add go-yamlvalidator tooling entry - #2514

Open
Yakwilik wants to merge 2 commits into
json-schema-org:mainfrom
Yakwilik:add-go-yamlvalidator
Open

Yakwilik wants to merge 2 commits into
json-schema-org:mainfrom
Yakwilik:add-go-yamlvalidator

Conversation

@Yakwilik

@Yakwilik Yakwilik commented Sep 27, 2026 •

Copy link
Copy Markdown

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-yamlvalidator to 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/jsonschema through dependsOnValidators, 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

@Yakwilik
Yakwilik requested a review from a team as a code owner September 27, 2026 02:46
@github-project-automation github-project-automation Bot moved this to Ready to review in PR - Triage Group Sep 27, 2026
@github-actions

Copy link
Copy Markdown

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

codecov Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (6e71690) to head (04f45bf).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Yakwilik

Yakwilik commented Sep 27, 2026 •

Copy link
Copy Markdown
Author

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready to review

Development

Successfully merging this pull request may close these issues.

Add go-yamlvalidator to JSON Schema tooling catalog

1 participant