openapi-processor / openapi-processor/openapi-processor-base
autodect Map<String, ComplexType> from `additionalProperties`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Kotlin
- Stars
- 2
- Forks
- 4
- Avg merge
- 4d 55m
- Merged PRs (30d)
- 9
Description
extracted from on openapi-processor/openapi-processor-spring/issues/150
if #10 works and produces maintainable code try to automatically detect a Map<String, ComplexType> from additionalProperties without an explicit mapping:
# ...
type: object
additionalProperties:
type: array
items:
type: string
or even more complex:
additionalProperties may contain an object that should be generated:
# ...
type: object
additionalProperties:
type: object
properties:
foo:
type: string
bar:
type: array
items:
type: string
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 reading issue #10 and tracing how additionalProperties is currently mapped in openapi-processor-base. Use the two schemas in this issue as cases: done means automatic Map<String, ...> detection without explicit mapping, including generated nested object types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100