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
I am currently implementing GET REST API with query parameters which gives large amount of JSON response body.
(it is not significantly large but not so small)
It return like below after I run "try it out.
Which works okay.
Response from server doesn't take so much time to send back the response. (below 200ms)
When scrolling down on "response payload" section on the document page, then if I want to move other area of the document,
browser is hung up for around 4 seconds.
Without clicking or scrolling in the "response payload", clicking other namespace or API works okay.
But this only happens when my mouse focused into the "response payload" section in the document page.
Any idea or help?
Is there any limit in RestX to display in response payload section?
The text was updated successfully, but these errors were encountered:
In a different life I think I remember a similar sort of issue, but the documentation wasn't generated with Flask-restx. Think it's caused by the implementation of the Swagger JS library.
I am currently implementing GET REST API with query parameters which gives large amount of JSON response body.
(it is not significantly large but not so small)
It return like below after I run "try it out.
Which works okay.
Response from server doesn't take so much time to send back the response. (below 200ms)
When scrolling down on "response payload" section on the document page, then if I want to move other area of the document,
browser is hung up for around 4 seconds.
Without clicking or scrolling in the "response payload", clicking other namespace or API works okay.
But this only happens when my mouse focused into the "response payload" section in the document page.
Any idea or help?
Is there any limit in RestX to display in response payload section?
The text was updated successfully, but these errors were encountered: