Andreas Haller

Hi. I think it makes sense to add more details to exceptions. I think it would be best to add `ResponseInvalidError#errors` or `ResponseInvalidError#failure.errors` to return an array of error objects...

By the way, if you use `request.validate_response(rack_response)` without passing `raise_error: true` you get an object where you can get all [details](https://github.com/ahx/openapi_first?tab=readme-ov-file#validate-response) including the response body. Somehing like: ```ruby response =...

Solved via https://github.com/ahx/openapi_first/pull/266

> What we don't want is someone assuming that the form can be submitted with blank required fields[…]. Why would any developer add required attributes to input fields and still...

You are not making it act the same way in all browsers, because it lacks the visual feedback, which is essential. I would rather like that behavior to be removed,...

> Maybe openapi_parameters should return the original value if it cannot be casted due to incompatible types. This is solved with [v0.3.4](https://github.com/ahx/openapi_parameters/releases/tag/v0.3.4)

Ping ⏰ @tzmfreedom Can you take a look at this? If you don't think you will find the time in the future I would be happy to maintain this gem.

Thanks for the report, @moberegger. > openapi_first dereferences them out when creating the schemas That is correct. I will have to take a deeper look if that’s an issue here....

Hey @moberegger I don't have a solution for this, but maybe a workaround: Maybe you can make use of one of the [JSON schema conditionals](https://json-schema.org/understanding-json-schema/reference/conditionals) instead of using `discriminator`? There...

I am happy to hear you found a solution to work around this issue 🔨 👍🏼. Also appreciate the positive feedback. I have not thought about it a lot, but...