-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Provide swagger generation options for ASP.NET Core Web API project template #7639
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
Comments
Removed the |
Can we get more background on this? Which provider does @danroth27 think we should go with, NSwag or Swashbuckle? Should we include SwaggerUI too? The title and description says "options", but what command-line option could there be other than "use swagger" (and "use SwaggerUI" if we want that)? We'll have to expose this as VS UI, have we talked with them about this? |
@ryanbrandenburg Please work with @glennc on this. |
From Glen:
|
note: that adding an external dependency like this requires a security review, even if we don't expect to find anything. |
Per in-person conversation with Glen I'm operating under the assumption that we won't be adding this option to F#. |
Moved this to |
Moving this to 3.1 because of the risks involved. |
We did this for 5.0. Swashbuckle is enabled by default for API project templates. |
The WebAPI project should be extended to support swagger generation options with one of the supported providers
The text was updated successfully, but these errors were encountered: