fix(swagger): Add dedicated endpoint for contents-ext root directory access #34930
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.
The contents-ext API has two routes - one for root directory and one for
specific paths, but only the path-specific endpoint was documented in Swagger.
This caused validation errors in auto-generated clients and Swagger UI when
trying to access the root directory.
Changes:
Fixes validation errors when using auto-generated API clients and Swagger UI
to access repository root contents via the contents-ext endpoint.