Added IncludeOpenAPIAnalyzers flag to the produced NuGet package
#2261
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/cc @dougbu |
pranavkm
reviewed
Jun 22, 2019
dougbu
added a commit
to dougbu/NSwag
that referenced
this pull request
Jun 23, 2019
dougbu
added a commit
to dougbu/NSwag
that referenced
this pull request
Jun 23, 2019
|
Thanks @dougbu. I'm closing this PR, as yours now includes the flag. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Rico.
In ASP.NET Core we've added a feature to the WebSDK to enable OpenAPI analyzers when the
IncludeOpenAPIAnalyzersflag is present. This change adds that flag to the NSwag.AspNetCore project, so that as soon as that NuGet package is referenced from an ASP.NET Core project, the API Analyzer is enabled./cc @pranavkm
Addresses dotnet/aspnetcore#8418