Currently the API definition generation does not include any happy path that produces a complete API definition. I would like to add at least one path from a blank function to the API definition such that it produces a complete API definition.
@soninaren is going to try to hack together a basic prototype this month
Any update on this?
I've spent around two workdays on an Azure function reflecting out a proper Swagger def for .Net. https://github.com/wobba/AzureFunction-SwaggerDefinition Needed it for a customer project and dows pretty much what Swashbuckle does. Might be missing pieces, but covers quite a bit for now.
This is the missing link for amazing integration with tools such as API Management and needs to work for v2 Functions. Supporting attributes such as ProducesResponseType, Produces, and Consumes would make a big difference.
Also take a look at https://devkimchi.com/2019/02/02/introducing-swagger-ui-on-azure-functions/ and the github repo for it https://github.com/aliencube/AzureFunctions.Extensions and the nuget package https://www.nuget.org/packages/Aliencube.AzureFunctions.Extensions.OpenApi/
Most helpful comment
Any update on this?