Open OskarNet opened 3 years ago
As the readme.md file explains it sounds like it should be enough to add the package build the project and run it and the Swagger endpoints should be created and be accessible.
@OskarNet Thanks for the issue. Here's the sample code project directly from the package, not from the project.
https://github.com/justinyoo/azfunc-openapi-dotnet
Would you please try this one? If it's working, please add Microsoft.Azure.WebJobs.Extensions.ServiceBus
, NLog
and System.Data.SqlClient
one-by-one to find out which package is impacting on you.
Right. I've added the extension to seven of my Azure Functions projects and most are working. Don't think it's the other packages that are the problem as I've removed them and still not working for a few of them. Continuing to investigate
Yeah, There are several issues reporting some other NuGet packages prevents the OpenAPI document from being rendered.
@OskarNet Can you try this workaround? https://github.com/Azure/azure-functions-openapi-extension/issues/281#issuecomment-942883598
@justinyoo Having this issue with this pair:
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.OpenApi" Version="1.3.0" />
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.ServiceBus" Version="5.6.0" />
Adding
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
Also doesn't work. When I add that, the swagger renders but doesn't pick up any operations - so I get an empty swagger
For now my only option seems to use the direct ServiceBus nuget (i.e. not the function app extensions one), which isn't ideal
Hi
I must be missing something but I'm unable to navigate to api/swagger/ui as RenderSwaggerUI and RenderSwaggerDocument are not shown as endpoints when running the functions project locally. I'm looking at the sample Microsoft.Azure.WebJobs.Extensions.OpenApi.FunctionApp.V3IoC as I've got an v3 Azure Functions project.
I'm using the latest version 0.8.1-preview
Project packages:
Any thoughts?
Regards, Oskar