Unfortunately, I'm not explicitly defining the JSON/YAML spec, it is autogenerated between springdoc which is built on top of swagger.
I am starting with @RequestParam MultiValueMap<String, String> requestParameter which I don't have the ability to change easily and the spec is built as noted in the original post.
So I guess there are two follow up questions:
1) Is the swagger UI parsing the generated structure as expected/desired? If so, any idea why postman would parse the same spec (OAS 3) differently? I would think both would parse it exactly the same, per the spec.
2) Per your recommendation, how would an underlying property of a parameter's schema be elevated to it's own parameter with it's own schema programmatically? I had thought the explode+form features would effectively do that per the documentation here:
https://swagger.io/docs/specification/serialization/#query
Object id = {"role": "admin", "firstName": "Alex"}
| form * | true * | /users{?id*} | /users?id=5 | /users?id=3&id=4&id=5 | /users?role=admin&firstName=Alex |
Does this not apply to a Map as a request parameter object with an underlying array property?
Thanks,
Matt
