OpenAPITools / OpenAPITools/openapi-generator
[REQ] Infer const type during 3.1 normalization
Open
Nobody has claimed this yet.
Enhancement: Feature
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
Some 3.1 schemas represent enumerations as oneOf consts without type. Current normalization doesn't convert such schemas to enums.
Describe the solution you'd like
During normalization, if a schema with const has no type, it should be inferred from the const value.
Example
# Input (3.1 schema)
oneOf:
- const: "foo"
- const: "bar"
# Expected normalized output
type: string
enum:
- foo
- bar
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 in the issue. Locate the OpenAPI 3.1 normalization entry point and existing normalization tests, then trace how oneOf const schemas are handled. Done means a const without type is inferred from its value and the example normalizes to a string enum.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100