-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[typescript] allOf fails with chained inheritance #13417
Comments
+1 |
I think this thread may be related: #10125 From my point of view, the workaround options are: a) use discriminators on all inherited types, or b) revert to v4.3.1 where inheritance was still supported without discriminators though personally I agree with others in that thread stating that discriminators should not really be required in this use case. |
We've added a rule Please give it a try when you've time. |
doesn't work with typescript-angular. you can put anything for normalizer options without a singly warn from it. Seems like normalizer is not applied at all |
My team also has issues with the paths:
/cobrand/v1/public/cobrands:
get:
allOf:
- summary: Get cobrands...
- description: User Session identifier ... ends up being an ugly and empty "/cobrand/v1/public/cobrands": {
get: {
};
}; |
How can I set up REF_AS_PARENT_IN_ALLOF=true in my pom.xml for plugin configuration? |
Bug Report Checklist
Description
Using openapigenerator 6.0.1, with generator "typescript".
If a spec uses
allOf
to specify an inheritance chain, the child in the inheritance chain will have its own properties and the properties of its most distant parent, but not the properties of its closest parent.In the provided example, the instance of class
Child
would haveChild.ChildAttribute
andChild.GrandparentAttribute
but notChild.ParentAttribute
.openapi-generator version
6.0.1
OpenAPI declaration file content or url
https://gist.github.com/MattiasMartens/49415a0fe5c3922500424d61c5a3c97a
Related issues/PRs
First raised in #927.
The text was updated successfully, but these errors were encountered: