-
Notifications
You must be signed in to change notification settings - Fork 271
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
Missing swagger_fake_view attribute #321
Labels
enhancement
New feature or request
fix confirmation pending
issue has been fixed and confirmation from issue reporter is pending
Comments
tfranzel
added a commit
that referenced
this issue
Mar 2, 2021
tfranzel
added
the
fix confirmation pending
issue has been fixed and confirmation from issue reporter is pending
label
Mar 2, 2021
Hi! i was hesitant to do this before as it felt like a cop-out, but i realize now that sometimes you are simply stuck there and all other option are worse. i mean we do generate mock requests with an anon user, but apparently that is not enough the cover all cases. so added the feature finally. 🚀 |
This is just wonderful, thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
fix confirmation pending
issue has been fixed and confirmation from issue reporter is pending
Hi. I'm using drf-spectacular with drf-nested-routers and faced an issue: whenever I'm raising Http404 inside
get_queryset
or before the method call, for example if the nested object does not exist, I get this warning when accessing Swagger schema view:I know that drf-yasg has a mechanism to distinguish a real view from the schema-generated one described in this issue axnsan12/drf-yasg#267:
Unfortunately I wasn't able to find something like that for drf-spectacular. Maybe I'm missing something or this could be a feature request. Thanks!
The text was updated successfully, but these errors were encountered: