You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: