[release/9.0] Fix handling for inert route parameters in MVC endpoints for OpenAPI #58311
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.
Description
Backport of #58246 to release/9.0.
This PR makes the OpenAPI implementation more resilient to "inert route parameters" in MVC. Inert route parameters appear in the route template but are never bound to in the route handler. For example:
This pattern happens frequently when users integrate with the API versioning package which uses inert route parameters to distinguish between different versions of an API.
Fixes #58219
Customer Impact
Without this PR, customers are not able to generate OpenAPI specs for APIs that are versioning with the API versioning package and use version numbers in the URL.
There are no workarounds for this issue.
Regression?
Risk
Change is localized to OpenAPI package and makes the package more resilient to bad inputs.
Verification
Packaging changes reviewed?