Skip to content

[BUG][PYTHON] Client response is not respecting capital letters #10469

@gmcrocetti

Description

@gmcrocetti

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

Python response containing keys in capital letters are being converted to lowercase. Therefore, schema is not being respect. I'm not sure if attribute map should be done at response time.

openapi-generator version

3.0.3

OpenAPI declaration file content or url
openapi: 3.0.3 info: title: Sample service version: 0.0.1 description: response wrongly capitalized paths: /foo: post: operationId: foo description: hello requestBody: content: application/json: schema: $ref: '#/components/schemas/MyRequest' responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/MyResponse' components: schemas: MyRequest: type: object properties: hello: type: string MyResponse: type: object properties: QUICK: type: boolean readOnly: true default: false FOX: type: boolean readOnly: true default: false required: - QUICK - FOX
Generation Details

Python client was generated with default settings using the docker image provided (latest)

Steps to reproduce
  1. Call your endpoint that returns capitalized letters. Response should be something like:
{ "QUICK": "foo", "FOX": "bar" }
  1. Python client parses response above and returns all entries in lowercase.
{ "quick": "foo", "fox": "bar" }
Related issues/PRs
Suggest a fix

It's ok controlling this in a request scenario, where the arguments to your class object are all lowercase but regarding the response, I don't this this parsing as valuable as API's consumer expects to receive a response matching the schema definition, which is not happening currently.
Expected output should mimic the schema:

{ "QUICK": "foo", "FOX": "bar" }

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions