-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Schema/OpenAPI: Make operationId camel-case #7208
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
Schema/OpenAPI: Make operationId camel-case #7208
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.
Hi @gnuletik. OK, this seems reasonable. If you rebase and adjust tests we'll go with it.
Thanks for the input!
1bfdce9
to
3300936
Compare
Thanks for the feedback! |
Super thanks. I think we just need one more rebase. 😀 |
7d2dbdd
to
200e839
Compare
200e839
to
d1c849e
Compare
I rebased it on master @carltongibson :) |
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.
Well done.
Finally! 😀
This PR intend to make the OpenAPI - AutoSchema's operationIds camel case and consistent across the schema.
The operationId in OpenAPI examples are all camel case.
e.g. : Do a CTRL-F for "operationId" on the spec
The current behavior is the following :
ViewSet
(with the inherited methods :get
,list
,retrieve
,partial_update
etc..), you will get anoperationId
likepartial_updateItem
which is halfsnake_case
and halfcamelCase
.get
,post
,put
etc...), you will get anoperationId
likeRetrieveItem
which is "PascalCase" or "upper camel case".With this PR, the auto-generated
operationId
will be camelCase.