openai / openai/openai-openapi
Mixing OpenAPI 3.0.x and 3.1.x
Open
Nobody has claimed this yet.
bug
specification
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 527
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 2
Description
most issues are coming from
nullable:true.
it should be
anyOf:
- type: ...
- type: 'null'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; begin by locating the OpenAPI schemas that still use nullable:true and compare them with the issue's OpenAPI 3.1.x example. Done means the affected definitions no longer mix 3.0.x nullable syntax with 3.1.x null typing, while preserving the intended schemas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100