[OpenAPI 3.1] Stage 1: OpenAPI 3.1 support

Open
#947 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
java, openapi
Domain
api, tooling

Research direction

This is an umbrella tracking issue, not a task: it carries no file, test or entry point, and the actual work lives in the Phase 0-4 sub-issues. Start by reading the parent plan at #942 and the phase sub-issues to find one scoped piece, then look at the diff engine that currently branches on spec version. Done means all phase sub-issues are closed and the 3.0.0 migration notes are complete, so no single newcomer can finish this alone.

Written by the indexing model from the issue text.

Description

OpenAPI 3.1.0 Support

Tracking issue for Stage 1 of the OpenAPI 3.1 plan: #942

Goal

Official OpenAPI 3.1 support in 3.0.0:

  • one diff engine for Swagger 2.0, OpenAPI 3.0 and 3.1
  • the same change gets the same verdict in every version
  • verdicts for 3.0 specs stay unchanged
Phases

Tracked as sub-issues of this issue (Phase 0–4).

Done when
  • All phase sub-issues are closed
  • 3.0.0 migration notes are complete
Dominant language
Java
Stars
1.1k
Forks
191
Avg merge
4d 23h
Merged PRs (30d)
1

Getting set up

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 OpenAPITools/openapi-diff

All issues in OpenAPITools/openapi-diff

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.