OpenAPITools / OpenAPITools/openapi-generator

[BUG] XML support for cpp-qt-qhttpengine-server generator

Open
#14,953 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue: Bug
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

I'm currently using this tool to generate QHTTP server stubs and am having trouble getting it to generate xml code for models I have defined in my yaml file.

openapi-generator version

Pulled the latest docker image from docker hub

OpenAPI declaration file content or url

Attached the yaml code to this issue.

Generation Details

To generate the code, I run the following:
docker run --rm -v "${PWD}:/local" openapitools/openapi-generator-cli generate -i /local/ped.yaml -g cpp-qt-qhttpengine-server -o /local --additional-properties=withXml=true

Steps to reproduce
  1. Generate the code
  2. In the generated model files, you will only see "asJson" methods created
Related issues/PRs
Suggest a fix

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the documented Docker generation command with the attached YAML and withXml=true. Inspect the generated model files and compare the available asJson methods with the expected XML support; done means the generated QHTTP server models include the intended XML handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.