fix(poem-openapi): handle additional_properties correctly in flatten #961
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the generated documentation for a type like
Currently, such a type shows no documentation for
items
, becauseHashMap<String, ...>
only containsadditionalProperties
in the schema. This PR adds tracking ofadditionalProperties
in addition toproperties
andrequired
when usingflatten
.In principle we can only support one flattened type with
additionalProperties
, but it wasn't clear to me how to enforce this, so instead this PR just keeps track of theadditionalProperties
of the LASTflatten
-ed field.