Altay Batuhan

Type declarations are needed

Thanks a lot @ferdikoomen !! Let me know if we can contribute in some way, thanks for keeping the library updated

@ferdikoomen unfortunately the fix doesn't help our case (from my original issue): ```As you can see the Pageable parameter is defined as object``` The fix only works for lists, not...

@ferdikoomen this is the openapi spec for pageable we are using: ``` { "Pageable": { "type": "object", "properties": { "page": { "minimum": 0, "type": "integer", "format": "int32" }, "size": {...

@ferdikoomen we were using npx. Specifying the version now, we got the same behavior as you do. However this behavior: ```pageable[sort]=LOCATION``` is very much different from the intended and swagger...

@ferdikoomen The generation is identical, however I think that nested query objects should be flattened to a key:value pair list, instead of having the nested structure stringified into parentkey[childkey]:value list....

No it is practically same: ``` { "get": { "tags": [ "foo-controller" ], "operationId": "bar", "parameters": [ { "name": "pageable", "in": "query", "required": true, "schema": { "$ref": "#/components/schemas/Pageable" } }...

@ferdikoomen Yeah, I will do some testing around it, let's see what is the actual behavior of swagger. May I ask how is the current behavior useful? If you could...

@ferdikoomen Immediately I tested an object as a request parameter, and the swagger generated using the same behavior, and the request is a bad request (as the response confirms). So...

@ferdikoomen Also, Tomcat throws an error when URL has "[" or "]": ``` Invalid character found in the request target [/foo/boo?pageable[sort]=LOCATION]. The valid characters are defined in RFC 7230 and...