Specify full schema for the value of MapOf, regardless of the key type#3732
Merged
Conversation
767819f to
1a135fc
Compare
Member
|
This makes sense, thank you for the PR! There seems to be an issue with the tests (https://github.com/goadesign/goa/actions/runs/15892630093/job/44863034090?pr=3732), I'll be happy to merge once this is fixed. Running |
1a135fc to
d840363
Compare
d840363 to
f0a6407
Compare
Contributor
Author
Hi @raphael, thanks for your quick response. |
Member
|
Great, thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue:
When using
MapOfin Goa designs, depending on the type of they key, we can have different results:additionalProperties+$refannotation)additionalProperties: true)Cause:
Goa generates OpenAPI 3 specs according to https://swagger.io/docs/specification/v3_0/data-models/dictionaries/, which states that
However, the condition (keys are strings) are implicit and cannot be changed any way (RFC 8259). So no matter what KeyType is in
MapOf(KeyType, ...), the results are the same, and any reader of the generated specs will interpret the map as having String key.So by using
additionalProperties: truewe lose information that would otherwise be useful for readers of the specs (for example, oapi-codegen wouldn't be able to properly generate the correct type).Solution:
Example:
Design
Current behaviour (as of v3.21.1)
New behaviour:
Compare:
(1): current = free-form, new = fully typed
(2): current = free-form, new = fully typed
(3): current = fully-typed, new = fully typed (same behaviour, because keys are strings)
(4): current = fully-typed, new = fully typed (same behaviour, because keys are strings)