-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
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
Performance degrades on swagger after migrante from restplus #558
Comments
The browser part of I suspect that given restplus is old, it is using a much earlier version of If you are rendering extremely long responses, you might want to render a custom template with syntax highlighting disabled (see swagger-api/swagger-ui#3832 and #430 (comment)) or consider paginating your output. |
How I determine the swagger-ui-dist version on a application? |
See https://swagger.io/docs/open-source-tools/swagger-ui/usage/version-detection/ If you are using firefox, press Ctrl+Shift+K whilst viewing your swagger docs, then enter {"swaggerUi":{"version":"3.52.0","gitRevision":"gee40b00","gitDirty":true,"buildTimestamp":"Mon, 09 Aug 2021 15:13:17 GMT","machine":"ip-172-31-21-173"}} |
How I could upgrade or downgrade the swagger-ui-dist version? |
The Because |
We have a backend service that is developed with restplus, it's works without a problem.
After migrated for restx we observed that some endpoints, that have big responses (>3MB) makes the tab of browser crash, and the browser suggests to interrupt
We are using restx version 1.1.0.
The response using curl work perfectly
The text was updated successfully, but these errors were encountered: