Is your feature request related to a problem? Please describe.
I prefer using NSwag over Swashbuckle because of better support for API Client generation. I would also like to use this library but that would mean having a dependency on NSwag AND Swashbuckle.
From another POV, This library would be great to use for OpenAPI spec generation. I don't think it's necessary to couple the Swagger UI to it.
Describe the solution you'd like
Perhaps this library could remove the dependency on Swashbuckle so it would be usable for NSwag/other OpenAPI library users.
Some ideas:
Create an endpoint that would return the OpenAPI definition. I can then configure NSwag/Swashbuckle/whatever to look at that endpoint for the definition
Create a method like public string GetOpenApiDefinition(); that returns the Swagger definition. I can then configure NSwag/Swashbuckle/whatever to call that method and use that as the OpenAPI definition.
Is your feature request related to a problem? Please describe.
I prefer using NSwag over Swashbuckle because of better support for API Client generation. I would also like to use this library but that would mean having a dependency on NSwag AND Swashbuckle.
From another POV, This library would be great to use for OpenAPI spec generation. I don't think it's necessary to couple the Swagger UI to it.
Describe the solution you'd like
Perhaps this library could remove the dependency on Swashbuckle so it would be usable for NSwag/other OpenAPI library users.
Some ideas:
public string GetOpenApiDefinition();that returns the Swagger definition. I can then configure NSwag/Swashbuckle/whatever to call that method and use that as the OpenAPI definition.Describe alternatives you've considered
None
Additional context
None