cancel
Showing results for 
Search instead for 
Did you mean: 

Openapi 3.0.1 in ReadyAPI 3.0.0

SOLVED
Highlighted
New Contributor

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?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Manager

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

Thank you richie, nmrao!

 

@ANRAPI , were you able to solve this yet? If not, opening a support ticket might be a good idea. 

 

 


Sonya Mihaljova
Community and Education Specialist

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today

View solution in original post

8 REPLIES 8
Highlighted
Community Hero

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

Hi @ANRAPI,

You dont actually mention what the problem is! 🙂

You ask about a solution and mention openapi v3.0, but whats actually happening?

Whats actually the response when you try and load in the file?
Are you sure that openAPI v3.0 is supported by ReadyAPI! V3.0?

Cheers

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
New Contributor

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
Highlighted
Community Hero

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

Here are couple of threads based on which it does not confirms support for OAS 3.0.1; it is currently support 3.0.0.

it is a bit old, but not updates (there is defect / enhancement regarding the same RIA-9609)
https://community.smartbear.com/t5/SoapUI-Pro/Support-of-openapi-3-0-1-specification-in-ReadyAPI/td-...

Latest version release notes with bug fix details and it does not have the above defect it
https://support.smartbear.com/readyapi/docs/general-info/version-history/bugs-fixed-in-ver-3-0.html

Best thing would be to open a support ticket and find the status of the issue and / or ETA for the fix.


Regards,
Rao.
Highlighted
Community Hero

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

Hi @ANRAPI,

Looking at your errors it appears that you might have errors in the content of the .json file itself, especially the last error. You might have some malformed/invalid detail in the file cos it appears at least from the last error it looks like you have an attribute value that doesnt correspond to a defined regex pattern.
Have you tried using checking the wellformedness/validity of the file via an online tool or something like a recent version of xmlspy (which includes .json wellformed/valid functionality)?

Id double check the file to ensure its ok and if not (as the errors may suggest) fix the file and then retry.

Id also check ReadyAPI!'s release notes regarding openAPI/swagger to double check if v3.0 is supported. If its not, then youll have to downgrade your opemAPI file to the earlier supported version.

Cheers,

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
Community Hero

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

@richie, Downgrading version in the swagger file would not be in the hands of QA engineers as certain features only work in specific version of swagger.


Regards,
Rao.
Highlighted
New Contributor

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

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
Highlighted
New Contributor

Re: 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

Highlighted
Community Manager

Re: Openapi 3.0.1 in ReadyAPI 3.0.0

Thank you richie, nmrao!

 

@ANRAPI , were you able to solve this yet? If not, opening a support ticket might be a good idea. 

 

 


Sonya Mihaljova
Community and Education Specialist

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements
TechCorner Leaderboard
Compete with community members in the TechCorner Challenge and get into the Leaderboard!

Rank Participant Points Earned
1 msiadak 12
2 nmrao 8
3 HimanshuTayal 3
Top Kudoed Authors