We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I realized that the error handling PR for API v2 (#1946) broke our Swagger UI docs.
See https://staging.sourcify.dev/server/api-docs/
returns:
{"customCode":"route_not_found","message":"The requested resource was not found","errorId":"cd41cfb4-b40e-4c3e-95f3-42f3a83bfe87"}
Seems like the swagger docs route is matched later than the 404 fallback.
The text was updated successfully, but these errors were encountered:
manuelwedler
Successfully merging a pull request may close this issue.
I realized that the error handling PR for API v2 (#1946) broke our Swagger UI docs.
See https://staging.sourcify.dev/server/api-docs/
returns:
Seems like the swagger docs route is matched later than the 404 fallback.
The text was updated successfully, but these errors were encountered: