OpenAPITools / OpenAPITools/openapi-generator
[REQ] Feature Request Description
Nobody has claimed this yet.
- 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.
I am building a Domain Model.
I have many yaml for different parts of the domain.
when I run these through -g OpenAPI I get all sorts of issues, but my principle one is that my $ref's are always resolved, I want to leave them unresolved.
Describe the solution you'd like
I want to leave them unresolved.
Describe alternatives you've considered
manually converting to Json, messing around with lots of data and then compiling it again.
Additional context
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
Start by locating the OpenAPI Generator entry point for YAML parsing and $ref resolution, then reproduce the behavior with the reported domain YAML files and the -g OpenAPI command. The work is done when a supported option or behavior preserves the references unresolved without requiring manual JSON conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100