-
Notifications
You must be signed in to change notification settings - Fork 2
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
Expanding content endpoints in Umbraco Delivery API is hanging when TypedSwagger is enabled #30
Comments
It seems to be related to this logic executing here, when TypedSwagger is enabled. |
Hi @bjarnef , I think the issue you are experiencing is most likely due to swagger-api/swagger-ui#6787, so slightly out of our hands. Just to confirm, the actual swagger json loads correctly, and only the UI is slow when you try to expand an operation? |
Hi @bjarnef Would you be able to confirm if doing the following solves your issues?
|
Hi @lauraneto I was only notable when expanding content endpoints, not media. I guess it is related to many content models including element types, where there often only are a few media types/models. Swagger UI loaded correctly, but expanding the endpoints made the CPU spike. However it also seems to have an impact on the Delivery API as the it seemed to shutting down on development environment on Umbraco Cloud. After we disabled |
It seems like this happens, when the EDIT: |
Which version of the package are you using?
12.0.0
Which Umbraco version are you using? For example: 12.2.0 - don't just write v12
12.3.9
Bug summary
I noticed on a project we have Delivery API extensions package enabled expanding content endpoints under Umbraco Delivery API made the application hanging until the browser failed.
We had this configuration:
after changing
TypedSwagger
withEnabled": false
the Swagger content endpoints expands just fine.Steps to reproduce
Expand any content endpoints under Umbraco Delivery API and notice difference with
TypedSwagger
enabled and disabled.TypedSwagger enabled
TypedSwagger disabled
Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: