Francesco Tumanischvili

After some clarification of current behavior with @char0n , we are closing this ticket as it currently doesn't impact performance, we will re-open and implement a solution as detailed below...

Thanks!

closing as inactive

fixed in #1681 and #1837

@Tvaroh please try with latest `1.6.1-SNAPSHOT` version which has some updated deps, possibly it could solve your issue

Hey @Mark-H, many thanks for your kind offer! We have 3.1 in our short term roadmap, we'll add an explanation in a few days about what we're doing and how...

As mentioned [above](https://github.com/swagger-api/swagger-parser/issues/1535#issuecomment-924045027) we have 3.1 in our short term roadmap, that we are sharing here, along with some design decisions taken to reach a good balance in terms of...

@gunsluo on its way, should be very short term for parser support including dereferencing. Swagger Core support for representation/serialization/deserialization has been implemented, along with OAS 3.0 conversion into 3.1 as...

#1730 implements OAS 3.1 Support in terms of parsing/validation and de-referencing / resolving. Updated documentation about usage, features, limitations and remaining tasks will follow shortly (Swagger Core and Swagger Parser)

@NarendraNallabelli are you still experiencing issues with latest versions (swagger-play 1.5.2)?