OpenAPI Schema Issues - Incorrect Inheritance and Polymorphism Definitions
in progress
A
Ali Al Kubaisi (eSwitch)
I've identified two issues in the OpenAPI schema that cause problems when generating client code with openapi-generator-maven-plugin:
Issue 1: Missing allOf in Child Schema Definitions
Child schemas that inherit from parent schemas are missing the allOf property to properly define inheritance relationships.
Issue 2: Incorrect Mixing of allOf and oneOf in Vehicle.requiredArea
The requiredArea property in the Vehicle schema incorrectly combines both allOf and oneOf, which causes ambiguous type definitions.
Since Polygon and MultiPolygon already extend/implement GeoJsonGeometry, the allOf reference is redundant and creates conflicts. Only oneOf should be used here to indicate that the field accepts either type.
Screenshots: in the screenshots you can find a possible solution and the location of the issues.
Screenshot 1: Missing allOf in BreakPlan
Screenshot 2: Incorrect allOf + oneOf mixing in Vehicle.requiredArea
Screenshot 3: Missing allOf in VisitPlan
Impact:
These issues prevent proper code generation and cause the OpenAPI generator to create incorrect or incomplete model classes.
Thanks for your support
Log In
Jurriaan Persyn
marked this post as
in progress
Hi Ali,
Thank you for flagging this bug! I’ve passed your report to our development team and we’ll make sure it’s handled correctly.
Quick note for next time: for bugs, it really helps if you email support@timefold.ai. Our support channel lets us classify issues by severity and process them according to our SLAs, so the right people can jump on it fast. This board is perfect for new feature ideas and discussion. You can find the guidelines here: https://docs.timefold.ai/timefold-platform/latest/feature-requests
Thanks again for helping us improve Timefold!
Regards,
Jurriaan Persyn