-
Notifications
You must be signed in to change notification settings - Fork 433
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
Question about Swagger support #441
Comments
It hasn't been updated in quite a while here but of course it'd be best for us to use the latest and greatest swagger! |
Ok, We already tested with the last packages and looks good. We have created branch locally and can push it if you give us access to do it. |
@GetTaxSolutions do a fork and open a PR and we will review |
Seeing PR #492 I don't think it is correct to use:
Instead of:
See README.md on top of this Github repository - domaindrivendev/Swashbuckle. The owner redirects us to his other Github repository - domaindrivendev/Swashbuckle.AspNetCore Also look at the most recent contributions to both repositories:
|
Hello,
In this project is using package Swackbucle.AspNetCore 1.0.0 for swagger implementation. But when I open the http://swagger.io site and download server side example for .Net core the packages which are included are Swashbuckle.SwaggerGen (>= 6.0.0-T2016120822) and Swashbuckle.SwaggerUi (>= 6.0.0-T2016120822) - (NOT Swackbucle.AspNetCore 1.0.0)
In packages description looks like that them support .Net Core and .Net standard v1.6.
What is the different between current package in use and these new packages v.6.0.0. What of them is better to be used in the future? I suppose that swagger team with continue with 6.0.0 support. What do you think about this?
Thank you
The text was updated successfully, but these errors were encountered: