autodect Map<String, ComplexType> from `additionalProperties`

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin, openapi
Domain
api, tooling

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.

Description

enhancement

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
Dominant language
Kotlin
Stars
2
Forks
4
Avg merge
1d 11h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openapi-processor/openapi-processor-base

All issues in openapi-processor/openapi-processor-base

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.