Skip to content
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

Version 3.0.39 on Azure Functions with OpenAPI spec give 'No operations defined in spec!' #3033

Open
saraaraujo-shell opened this issue Oct 25, 2023 · 0 comments

Comments

@saraaraujo-shell
Copy link

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

  1. Set up a HTTP triggered azure function with Open API annotations
  2. Install version 3.0.39 of Microsoft.Azure.WebJobs
  3. Run the function and open the /api/swagger/ui path

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

  • Package version
    3.0.39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant