-
Notifications
You must be signed in to change notification settings - Fork 43
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
Strange exception when open swggaer doc -> TypeError('Injecting Any is not supported') #78
Comments
Hey @M1LKYWVYs, thank you for a really precise and well written bug report – it's appreciated. I'm sorry you're experiencing issues. This library does some shady things behind the scenes to make things work and that will interact weirdly with some other libraries. I don't have resources to investigate this for the time being, unfortunately. |
Hi, I am facing the same issue. According to my debugger it is related to the url_for method which 7th parameter **values has a type hint "t.Any". Were you able to find a workaround by chance? Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
@M1LKYWVYs @Bartolomeo624 |
@wsz Worked perfectly for this error using apiflask. Thank you! |
No update on this issue? =/ |
Any updates on this issue? Meet the same issue: TypeError: Injecting Any is not supported when trying to render_template even though I did not add |
Hi! I am facing very strange behaviour when trying to open swgger doc provided by flask smorest.
When trying to open swagger page (http://127.0.0.1:5001/application/swagger-ui) application falls down with error TypeError('Injecting Any is not supported').
I have removed all bindings to make example more understandable and clear, so sources:
My pyproject:
Everything works fine if remove injector (comment line 40
setup_app_injector(flask_app=flask_app)
).Full trace:
For someone who facing similiar problem -> Add flasgger to provide openapi documentation to your application.
The text was updated successfully, but these errors were encountered: