Request validation does not support nested query parameters

[gburgett]

First, thank you so much for building an amazing library! It has helped us a lot in development of our new API, since we started with a documentation-driven approach. It allows us to ensure our implementation matches our spec. Please forgive me if this is a duplicate but I couldn't find it in your issue history.

We have some query parameters for an index operation that are defined as "filters" with a nested key for the attribute being filtered on. An example is GET /api/v1/events?filter[slug]=%2Ftest. Rack's Query Parser implementation turns the above into this params hash:

{
  "rack.request.query_string"=>"filter%5Bslug%5D=%2F",
  "rack.request.query_hash"=>{
    "filter"=>{
      "slug"=>"/test"
    }
  }
}

And then we get the following validation error:

#/paths/~1events/get missing required parameters: filter[slug]

Since it is a Rack specific behavior I didn't think this issue belonged in the openapi_parser library.

Thanks again!

[ota42y]

Thank you for reporting!
A little more question, how do you describe the parameters in the OpenAPI definition?
Since there is a style: deepObject in the Parameter Object of OpenAPi 3, it may be possible to express it.
(If this example is intended and validation fails, it's a bug)
https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#style-examples

paths:
  /events:
    get:
      parameters:
      - name: filter[slug]
        in: query
	style: deepObject
	explode: true
        schema:  
          type: object
          properties:
	    filter:
	      type: string

[ahx]

Is this solved via #460 ?

[geemus]

@ahx Sorry, I looked over this a bit, but it wasn't clear to me if it's resolved or not. Maybe somebody with more direct context can give it a try and report back?