OpenAPITools / OpenAPITools/openapi-generator
[BUG] [csharp-netcore] Explode on queries not resulting in correct url
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 (example)?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
When generating with the attached schema where a query parameter is referencing an object, the called url doesn't explode the parameters despite me specifying it to do so.
openapi-generator version
5.3.0
OpenAPI declaration file content or url
Generation Details
openapi-generator-cli generate -g csharp-netcore
Steps to reproduce
Generate classes using the provdied schema. I expected the calling url to be https://localhost/users/?limit=10&skip=0, but it's something in the line of https://localhost/users/?ListQueryParams=class ListQueryParams {%0a Limit%3a 0%0a Skip%3a 0%0a }%0a
Related issues/PRs
N/A
Suggest a fix
N/A
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 with the OpenAPI schema in the linked gist and run the documented csharp-netcore generation command against it. Inspect the generated client request for the object-valued query parameter and compare it with the expected exploded URL; done means the generated call uses separate limit and skip query parameters instead of serializing the object.
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
- 35/100