-
Notifications
You must be signed in to change notification settings - Fork 4
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
Make operationId mandatory #182
Comments
I'm wondering about the "RECOMMENDED to follow common programming naming conventions". Doesn't that mean it would depend on the targeted programming language:
Or do code generators generally take care of converting operationId getEnterprise to GetEnterprise for C#, and get_enterprise for python? |
openapi-generator seems to convert to language-specific conventions, tested with python-flask, e.g. Works for other elements as well (without modification in the openapi), e.g.:
|
WG: OK to mandate operationId. Prefer to have lowerCamelCase as naming convention, consistent with property naming convention. |
Add a guideline that operationId MUST be present for each operation:
Empty operationId found for path: get /someResource. Renamed to auto-generated operationId: someResourceGet
Further guidelines in the OpenAPI spec about the operationId seem sufficiently clear (we refer or copy them):
The text was updated successfully, but these errors were encountered: