ContributionsMost RecentMost LikesSolutionsRe: Openapi 3.0.1 in ReadyAPI 3.0.0 In the OpenAPI 3.0.1 we use customised attributes - probably that's the cause it doesn't work Re: Openapi 3.0.1 in ReadyAPI 3.0.0 richie 1/ In Ready API docs I find this : Features Added to ReadyAPI 2.7 / Overall improvements / Support for OpenAPI specifications ver. 3.0.1 and 3.0.2. So I should think that it works also in Ready API 3.0.0 2/ when I use a json validator: it says it's valid jsonfile - I'll ask the devs to double check it for me Re: Openapi 3.0.1 in ReadyAPI 3.0.0 richie Recently we have updated the Json-files {"swagger":"2.0",...} to {"openapi":"3.0.1",...} It worked well with version 2.0. If I add the API with Json {"openapi":"3.0.1",...} the following type of errors is given: 1/ attribute paths.'/api/v1/...'(post).swaggerIgnore is unexpected 2/ attribute components.schemas.Support.Api.Controllers.OAuth.ClientCredentialGrant.ClientCredentialGrantWithAllScopesRequest.additionalProperties is not of type `object` 3/ attribute components.schemas.Schema name Infrastructure.Api.Hydra.HydraCollection doesn't adhere to regular expression ^[a-zA-Z0-9\.\-_]+$ I'm not sure that openAPI v3.0 is supported by ReadyAPI V3.0 Openapi 3.0.1 in ReadyAPI 3.0.0 I'm working with ReadyAPI 3.0.0. I want to add API from Swagger/OpenAPI Definition 5REST) with Jsonfile {"openapi":"3.0.1",... It worked well in the previous version of swagger jsonfile {"swagger":"2.0",... Has anyone a solution? Solved