We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On upgrading from version 3.0.37 to 3.0.39, the swagger file automatically generated on an Azure Function with OpenAPI spec comes with empty paths
Provide the steps required to reproduce the problem
The Swagger file to be automatically generated with the OpenAPI annotations given
'No operations defined in spec!' error
Works fine on version 3.0.37
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On upgrading from version 3.0.37 to 3.0.39, the swagger file automatically generated on an Azure Function with OpenAPI spec comes with empty paths
Repro steps
Provide the steps required to reproduce the problem
Expected behavior
The Swagger file to be automatically generated with the OpenAPI annotations given
Actual behavior
'No operations defined in spec!' error
Known workarounds
Works fine on version 3.0.37
3.0.39
The text was updated successfully, but these errors were encountered: