Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Upgrade schema to JSON Schema v2020-12

Open
#7 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
json
Domain
tooling

Research direction

Inspect the existing Draft 7 schemas in the Vega directory and review the conversion output from the linked alterschema tool. Add a v2020-12 directory containing the converted schemas, then verify that the new files represent the existing schemas under JSON Schema v2020-12 and align with OpenAPI v3.1 usage.

Written by the indexing model from the issue text.

Description

Using this tool, the existing Draft 7 schema can be converted to v2020-12. The new version has also been adopted as the official version in OpenAPI v3.1.

However, the tooling is yet to catch up with the new version and therefore, I would suggest that we maintain a v2020-12 directory inside the Vega directory for specifying these schemas.

Dominant language
No language data
Stars
42
Forks
25
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vega/schema

All issues in vega/schema

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.