Loss of opaque names for simple types

[MF1-MS]

Description

I am trying to wrap a primitive type such as a string with an opaqueWrapper. This is correctly rendered using swagger, but OpenAPI 'sees through' the wrapper and the underlying primitive type appears in the method signatures of the resulting generated code.

openapi-generator version

current master

OpenAPI declaration file content or url

definitions:
  request:
    type: object
    required:
      - opaque
    properties:
      opaque:
        $ref: '#/definitions/opaqueWrapper'

opaqueWrapper:
  type : string
  description: A string in an opaque format.

Command line used for generation

Steps to reproduce

Related issues/PRs

Suggest a fix/enhancement

[bjgill]

Hmm. I'm not sure whether this is a rust-server-specific problem or not.

[bjgill]

In fact, I think this comes from DefaultCodegen.java:fromRequestBody

        Schema schema = ModelUtils.getSchemaFromRequestBody(body);
        if (StringUtils.isNotBlank(schema.get$ref())) {
            name = ModelUtils.getSimpleRef(schema.get$ref());
            schema = schemas.get(name);
        }

It looks as if we're deliberately throwing the outer wrapper away.

[bjgill]

@wing328 - it looks as if this change was made in 5359776 (Add OpenAPI spec 3.0 support (beta)). Do you remember why this change was made (and/or have any ideas how to turn this behaviour off)?

[bjgill]

I think I've got a fix for this issue for rust-server. I'm hoping to be able to deliver it within the week.