ewaostrowska

Hi @EmhyrVarEmreis , Thanks a lot for coming up with the solution and putting in the work on this! I’ve created a follow-up PR here: https://github.com/swagger-api/swagger-core/pull/4950 based on your changes....

The issue has been fixed in [#5004 ](https://github.com/swagger-api/swagger-core/pull/5004) and will be included in the next release. Thank you @Yaytay for providing the solution

Hi @jochenberger! I’ve reviewed your PR and it does indeed restore enum and ref support in OAS 3.1 for ArraySchemas. I have created [a PR](https://github.com/swagger-api/swagger-core/pull/4949) based on yours to confirm...

There are still some failing tests in `APIResponsesResourceTest.java`. Please adjust tests :)

@bharattomar does the solution provided above solve your issue?

Hi @Curs3W4ll Thank you for reporting this issue. I have analyzed it and indeed it seems that the currant behavior is not correct for the parameters with external refs. Usage-site...

Hi @kuntal1461, Thanks a lot for providing the PR, it is a step in the right direction to resolve Validation Meta annotations issue. To be able to merge these changes...

Hi @jongmin-chung! Thank you for pointing this out. It does seem like mapping a numeric byte to integer/int8 would be conceptually correct for OAS 3.1 and is a change we...

Hi @dbr-cbk I have tried to reproduce the behavior you had reported but failed. Here's the test I have written (main.yaml and fragments.yaml are copied from this issue). Can you...