-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenAPi handler creates types with the same properties as separate types #1414
Comments
Thanks for opening this issue! |
Here are the relevant paths
|
Thanks! @chompy18 We'll take a look and get back to you soon! |
Cool, thanks. |
Another note that might be important here - when using |
We are currently rewriting the OpenAPI handler and releasing it as newOpenapi In this new handler, we resolve entire schema by dereferencing $refs then recreate definitions with $ref so this helps us to deduplicate the types that have the same properties.. I'd recommend you to check it :) So we can close this issue as it is covered by the handler. |
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Given a swagger definition, the OpenApi handler creates multiple types that contain the same properties.
Out of those types, they DO use the same 3rd type internally.
This makes using Fragments impossible, since fragments require to be defined on a specific type.
Note, that both
TranslationsListListItem
andTranslation
have exactly the same structure, but are separate types.Moreover, they both use the same
DisplayName
type internally.Talking with @ardatan , he suggested opening an issue because that's an inconsistency in the handler
The text was updated successfully, but these errors were encountered: