Thank you for providing this library.
Generic (error) responses built from ControllerAdvice exception handlers are built in an undefined order. In cases where multiple exception handler methods declare the same response status, which method’s return type ends up being used as the response schema for that status code is nondeterministic (might change between runs).
I’m speculating the issue is due to the use of the Set data type in iteration:
|
for (Map.Entry<String, ApiResponse> entry : apiResponses.entrySet()) { |
Thank you for providing this library.
Generic (error) responses built from
ControllerAdviceexception handlers are built in an undefined order. In cases where multiple exception handler methods declare the same response status, which method’s return type ends up being used as the response schema for that status code is nondeterministic (might change between runs).I’m speculating the issue is due to the use of the
Setdata type in iteration:springdoc-openapi/springdoc-openapi-common/src/main/java/org/springdoc/core/AbstractResponseBuilder.java
Line 74 in cca0857