OpenAPITools / OpenAPITools/openapi-generator
[BUG] [C#] [GenericHost] Breaking change in path handling since v7.13
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
Description
Our OpenAPI spec contains a servers block at the bottom, similar to this:
"servers": [
{
"url": "/some-path"
}
]
This path would then be used in ClientUtils.CONTEXT_PATH as a path prefix for all endpoints.
But because of the changes in this PR #20896 this no longer works ( @devhl-labs ).
Our auto-generated NuGet packages now no longer work because this path is missing.
Is the servers block of the OpenAPI spec no longer supported? Is there a better/new way to set a prefix path for all endpoints? Or is this simply a bug?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing C# GenericHost output before and after v7.13, focusing on ClientUtils.CONTEXT_PATH and the path-handling changes in PR #20896. Reproduce the issue with the provided OpenAPI servers URL and verify that generated endpoint URLs and the resulting NuGet package retain /some-path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100