Wrong generation on generic model parametrized by a collection

[egorklimov]

Hi!

My Quarkus app has a wrapper for an API response with a generic field.
I noticed that if my endpoint returns something like Response<List<Cat>>, my openapi model will look like this:

      "ListCat" : {
        "type" : "object",
        "properties" : {
          "empty" : {
            "type" : "boolean"
          }
        }
      },

Expected result:

      "ListCat" : {
        "type" : "array",
        "items" : {
          "$ref" : "#/components/schemas/Cat"
        }
      },

After some reverse engineering, I added this test case (as an example) to 'GenericModelTypesResourceTest': egorklimov@8c329f4

Test result is the same:

      "ListPOJO" : {
        "type" : "object",
        "properties" : {
          "empty" : {
            "type" : "boolean"
          }
        }
      },

Could you please confirm that this is actually a bug?

P.S.
Also, I noticed that while processing a field of type List<String> in SchemaRegistry#checkRegistration it has type array, whereas when processing a generic field parametrized by List (type.toString() -> "T") it has type object.

[egorklimov]

Seems that it is related to #387

When we resolve the type of a parameterized field, we must check whether it is a collection or not, and change the type to an array, if necessary