- Notifications
You must be signed in to change notification settings - Fork302
Adhered to field naming format setting when generating schema#1048
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks for working on this. Could you please also add a test which adds those cases?
I guess easiest is to extend theAuthorViewSet
so it covers the cases which are fixed in this PR. The tests intest_openapi.py
use snapshots so once the view has all the different cases added the snapshot only needs to be updated (pytest --snapshot-update).
@jokiefer Wanted to follow up whether you are still interested in working on this PR? |
I had some time at hand and wanted to make sure that this PR lands in the next version (which is hopefully released soon, waiting for DRF to release a new version supporting Django 4.1). I added a test and made minor adjustments to the PR. When adding the test, I noticed that there was actually an error in the code. It called Anyway. Thanks for bringing this up and working on it. |
Uh oh!
There was an error while loading.Please reload this page.
Description of the Change
Added additional field name formatting which got missed out in PR#1003
Checklist
CHANGELOG.md
updated (only for user relevant changes)AUTHORS