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
Hi, currently we've faced the issue on our project:
OpenAPIV3Parser.resolve() is wrapped with the try-catch and when any error occurs within it, e.g. path is incorrect or a component is wrongly defined, the exception is thrown and caught by that try-catch (typical try-catch behaviour). In this way the spec validation stops and not proceeded to further paths and components:
privateSwaggerParseResultresolve(SwaggerParseResultresult, List<AuthorizationValue> auth, ParseOptionsoptions,
Stringlocation) {
try {
// any exception here stops the spec parsing
} catch (Exceptione) {
LOGGER.warn("Exception while resolving:", e);
result.getMessages().add(e.getMessage());
}
returnresult;
}
It would be perfect to collect all such errors and not to get limited to a single one.
Please tell if it's possible,
Many thanks!
The text was updated successfully, but these errors were encountered:
Hi, currently we've faced the issue on our project:
OpenAPIV3Parser.resolve() is wrapped with the try-catch and when any error occurs within it, e.g. path is incorrect or a component is wrongly defined, the exception is thrown and caught by that try-catch (typical try-catch behaviour). In this way the spec validation stops and not proceeded to further paths and components:
It would be perfect to collect all such errors and not to get limited to a single one.
Please tell if it's possible,
Many thanks!
The text was updated successfully, but these errors were encountered: