Skip to content
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

Reorganizing Configuration Options in SwaggerConfig.cs installed via Nuget package #500

Closed
patrickjrs opened this issue Sep 16, 2015 · 1 comment
Milestone

Comments

@patrickjrs
Copy link

Hi,

Just wanted to document this here as I just spent a good deal of time on trying to figure out why my changes applied via custom OperationFilter were getting overwritten. Turns out using the IncludeXmlComments option adds an OperationFilter called ApplyXmlActionComments and a SchemaFilter called ApplyXmlTypeComments. Since the SwaggerConfig.cs file had a bunch of commented out configuration options I naively just uncommented what I needed and replaced with my own filters assuming it would all just work fine. Could be helpful when getting started with Swashbuckle to have the commented out options ordered so that anything custom added would not get overwritten. Or perhaps highlight the filter order in the docs.

@domaindrivendev
Copy link
Owner

See v5.2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants