Andreas Haller

> That sounds good to me. I think the only other thing is that `data_pointer` should change to `""` as well—does that seem right to you? That makes total sense

Hey @moberegger. Oh noes, it looks like the change introduced with 2.2.0 came with a few issues 🤦🏼. I think you are right in all aspects.

Hey @moberegger I have worked a little on this issue [over here](https://github.com/ahx/openapi_first/tree/fix-parameter-schema-ref). Maybe you can take a look at that. I will leave that there for a few days I...

I can work on a fix for this, unless you want to take this on.

Yes. This is a problem. The initial approach was to dereference the parameter schemas before they get passed to openapi_parameters, but I think we can discard that approach now. For...

FYI: I have two failing tests about this, parameter and reponse header validation, on [this branch](https://github.com/ahx/openapi_first/tree/fix-parameter-schema-ref). - https://github.com/ahx/openapi_first/blob/fix-parameter-schema-ref/spec/middlewares/request_validation/query_parameter_validation_spec.rb#L118 - https://github.com/ahx/openapi_first/blob/fix-parameter-schema-ref/spec/middlewares/response_validation/response_header_validation_spec.rb#L52

I have not looked at this again in detail, but my current thought about this is to stop merging all parameter schemas and change parameter validation to run each parameter...

This should be fixed on main via https://github.com/ahx/openapi_first/pull/342. It uses a little bit more memory now. I’ll do a new release in the coming days. It would be great if...

This is great. Being able to use the default `"rack.response_finished"` or `Rack::RACK_RESPONSE_FINISHED` as [specified by rack](https://github.com/rack/rack/blob/main/SPEC.rdoc#label-rack.response_finished) would be super helpful, because we could make use of `Rack::Lint` and would help...

> @ahx Hey, I'd totally welcome making this compatible with the RFC. Would it be possible to submit a PR that brings it up to spec, and then I can...