-
Notifications
You must be signed in to change notification settings - Fork 166
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
Let's use ref_name for nested embedded fields as well #284
Comments
Hello, @krsteve. I've never tested DRF-Mongoengine with Swagger spec support, and definitely cannot guarantee that they work together. To be honest, I've switched to other projects full-time and have not really been maintaining DRF-Mongoengine now. Do you suggest that addition of Thanks for your suggestion. Could you, maybe, create a unit-test for this functionality and submit a pull-request? I'll review it and merge, if everything works. |
Sadly I don't think I have the time to create a unit-test as I'm currently working way past hours... :( Anyways, great package! Helped me a lot. Thanks :) |
@BurkovBA @krsteve Take a look at #281, we ran into this problem in the beginning of 2021 and solved, deployed and run this successfully in production using drf-yasg. Unfortunately I can't invest time into adding unit tests in the foreseeable future, as we migrated our application to fastapi and I am busy with the last semester before my Bachlor thesis. |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
@skeletorXVI Sorry for my non-existence. Reviewed the PR, merged. Thank you for submitting it! |
Hi,
I'm using drf-mongoengine with drf-yasg, and terrible things happen with the Swagger spec generation because the ref_name is "Embedded" across all the nested embedded fields.
I was able to fix this issue by adding a ref_name line for the
build_nested_embedded_field
method ofDocumentSerializer
.The following link is the fork repo I'm using for my project. If you like this idea, please add this feature!
lessbutter@52da614
The text was updated successfully, but these errors were encountered: