Fix: Support nested query parameters defined with square brackets

[jalyna]

Currently I have the problem that parameters that are noted with square brackets, are not validated correctly. I use committee and all rack params are of course nested correctly.

I think semantically this should be the same and the values should be valid.

I have written some test cases and added a sample API definition.

I would be very happy to receive feedback.

[ota42y]

Sorry for my late reply.
There are no such rules in the OpenAPI 3 definition, so the current behavior is probably correct.
If you add rules that go against the original definition, people expecting rules to follow the definition will be troublesome (Perhaps the number is small) .

But I think this change useful.

What we want to do is this convert.

         - in: query
            name: nested_but_flat_object[name]
            required: true
            schema:
              type: string
         - in: query
           name: nested_but_flat_object[value]
           required: true
           schema:
             type: string
             format: date-time

        - in: query
          name: nested_object
          required: true
          schema:
            type: object
            properties:
              name:
                type: string
              value:
                type: string
                format: date-time

I think there is no desire to switch these conversions dynamically.
Therefore, there is no need to perform this conversion at runtim.
We can do pre-convert or post-convert to OpenAPIParser :: Schemas :: OpenAPI object.

I think it is good to provide pre or post convert method like this

 # preconvert pettern
 converted_yaml = OpenAPIParser.convert_nested_query_parameter(yaml)
 root = OpenAPIParser.parse(converted_yaml)
 # postconvert pettern, 
 root = OpenAPIParser.parse(converted_yaml)
 converted_root = OpenAPIParser.convert_nested_query_parameter(root) 

In this case, the validation rules are same as defined in the OpenAPI, and we can provide the above conversions to those who need them.
If it is found useful by various people, we can add this convert to OpenAPIParser.parse method with option flag.

[ota42y]

sorry for the late reply

[ahx]

@jalyna Can you share with what solution/workaround you ended up with in the end?