-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Path grouping strategy #3152
Path grouping strategy #3152
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #3152 +/- ##
=======================================
Coverage 83.25% 83.26%
=======================================
Files 76 76
Lines 3142 3143 +1
Branches 526 526
=======================================
+ Hits 2616 2617 +1
Misses 526 526
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
src/Swashbuckle.AspNetCore.SwaggerGen/SwaggerGenerator/SwaggerGeneratorOptions.cs
Outdated
Show resolved
Hide resolved
test/Swashbuckle.AspNetCore.SwaggerGen.Test/ConfigureSwaggerGeneratorOptionsTests.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you change this to 7.2.0 please?
<VersionPrefix>7.1.1</VersionPrefix> |
Wait. I will change exception message |
I was just about to enable auto-merge on this - what are you changing? |
Users can write function to generate path grouping.
For example, I can write path with
/myPath?queryParam1?queryParam2
, so I will not haveSwaggerGeneratorException
(Conflicting method/path combination x for actions (...)
) when mapping old .NET Framework API withRoute("/api/[controller]")
.Maybe related to #2354, but I don't know if
ApiDescription
has information aboutConsumesAttribute
.