openapi-processor / openapi-processor/openapi-processor-base
generate dto even though it has a mapping
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2
- Forks
- 4
- Avg merge
- 4d 55m
- Merged PRs (30d)
- 9
Description
Maybe it would be nice to create a mapping and still generate the dto for the OpenAPI type.
That way it would be possible to enhance (extend or wrap) the dto, by adding some "code" and use the enhanced version in the endpoint interface.
The mapping could use a new arrow operator to configure this
- type: OpenApiType => io.openapiprocessor.JavaType # standard
- type: OpenApiType +=> io.openapiprocessor.JavaType # i.e., generate dto for OpenApiType and use mapping
- type: OpenApiType -> io.openapiprocessor.JavaType
- type: OpenApiType ~> io.openapiprocessor.JavaType
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
The issue names no files, tests, or entry points. Start by locating the mapping parser and DTO generation logic, then determine how a mapping could preserve generation and how the proposed arrow variants should behave; done means the chosen syntax is implemented with coverage for generation, mapping, and enhanced DTO use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, openapi
- Domain
- backend-api-design, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100