You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adjusting the example in 2c46c1f did not fix the underlying issue with what object schemas are generated.
As the swagger-core uses the existing classes to generate the schemas used in the OpenApi specs, it will traverse all class dependencies down and resolve everything it can.
This leads to recursive dependencies, which break the API playground on staging. (It resolves all linked schematics and currently can't handle recursive schemas in the preprocessing step.) https://staging.openrouteservice.org/dev/#/api-docs
Is there an existing issue for this?
Problem description
Adjusting the example in 2c46c1f did not fix the underlying issue with what object schemas are generated.
As the swagger-core uses the existing classes to generate the schemas used in the OpenApi specs, it will traverse all class dependencies down and resolve everything it can.
This leads to recursive dependencies, which break the API playground on staging. (It resolves all linked schematics and currently can't handle recursive schemas in the preprocessing step.)
https://staging.openrouteservice.org/dev/#/api-docs
Proposed solution
See overriding models for how swagger-core operates and what can be done about adjusting the generated model.
Also see https://github.com/GIScience/openrouteservice/blob/main/ors-api/src/main/java/org/heigit/ors/api/responses/snapping/geojson/
The GeoJSONFeature.java works properly. Maybe something can be borrowed from there as well.
Additional context
No response
Forum Topic Link
No response
The text was updated successfully, but these errors were encountered: