OpenAPITools / OpenAPITools/openapi-generator

[BUG] it seems that cpp-qt5-qhttpengine-server doesn't support form data(x-www-form-urlencoded)

Open
#9,685 0 comments 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 am using openapi-generator to generate qt server stub(-g cpp-qt5-qhttpengine-server). I found that the generated stub code doesn't handle form param correctly, only define the vaiables and do nothing. and I want to handle it myself manually. but it seems the underlying library qhttpengine actually dones't support form data, it only support body in json format. But I can not find any statement in cpp-qt5-qhttpengine-server or qhttpengine said that it doesn't support form data. So am I wrong, or something wrong?

openapi-generator version

5.1.1

OpenAPI declaration file content or url

I only paste some part of it, actually, all form parameter have this probolem.

        "/mytest/CreateTestEntity": {
            "post": {
                "description": "",
                "consumes": [
                    "application/x-www-form-urlencoded"
                ],
                "produces": [
                    "application/json"
                ],
                "tags": [
                    "mytest"
                ],
                "summary": "CreateTestEntity",
                "parameters": [
                    {
                        "type": "string",
                        "description": "Token",
                        "name": "token",
                        "in": "header",
                        "required": true
                    },
                    {
                        "type": "string",
                        "description": "",
                        "name": "name",
                        "in": "formData",
                        "required": true
                    },
                    {
                        "type": "integer",
                        "description": "",
                        "name": "intValue",
                        "in": "formData",
                        "required": true
                    }
                ],
                "responses": {
                    "200": {
                        "description": "OK",
                        "schema": {
                            "$ref": "#/definitions/netmodel.CreateTestEntityResult"
                        }
                    }
                }
            }
        }
Generation Details
Steps to reproduce
Related issues/PRs
Suggest a fix

I just want to known whether this is a desired behavior, if it is, could the document be updated.

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 reproducing generation with the provided application/x-www-form-urlencoded specification and the cpp-qt5-qhttpengine-server generator. Inspect the generated handling of the formData parameters and determine whether the limitation belongs to the generator or qhttpengine. Done means establishing the intended behavior and either documenting the limitation or identifying a concrete fix scope.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.