-
Notifications
You must be signed in to change notification settings - Fork 27
error on creating project out of swagger spec #3
Comments
Hi! you will need to use the latest swagger plugin (version 2.0) available from the plugin-repository from within SoapUI Pro 5.X or Ready! API to be able to import Swagger 2.0 specs - can you give that a try? thanks! /Ole |
Same problem here (basepath) ... with the latest version of the plugin directly downloaded from Ready! API. |
I am also facing the same issue with ReadyAPI1.2.1 any help much appreciated |
@olensmar I am using the v2.0 and ready API 1.2.1 could you please help me |
thanks guys - an update of the plugin is in the making - if any one of you could share your swagger specs with me so I can make sure they work that would be grand - please send to [email protected] if possible! /Ole |
@olensmar Thank You very much currently we have local instance which you can't access |
The sample specs @ http://editor.swagger.io/#/ fails to load (I tried others, same error). Thanks ! (P.S. working for a multinational bank right now and about to include SoapUI as a main testing component) |
thanks for your input @pvdyck |
@pvdyck I've sent you an update of the plugin - please let me know how it works so I can either fix or publish. Thanks all! |
ok - the plugin seems to work now - anyone else want to give it a try before we publish it? Thanks in advance /Ole |
@olensmar YGM. Included an example I'm working on right now. Same errors when using the Petstore examples. Willing to test the plugin, let me know. great work, |
Guys - the new version of the plugin (2.1) is live in the plugin repository - if you have any issues please let me know! Thanks for your help! /Ole |
@olensmar I just tried, i'm not able to load a 2.0 spec. |
darn! can you share the spec? |
@olensmar this is it. http://pastie.org/private/kzvoxwn2eh5xr4anfdth1a Also this is the console log
|
@olensmar any development on this issue, how can I help? |
not yet - i'll fix it over the weekend - sorry to keep you waiting! |
Thank you! On Fri, Apr 17, 2015 at 12:09 PM, Ole Lensmar [email protected]
Sebastián Ortiz Vásquez. |
ok - i've dug in - the cause of this is that the Swagger parsers internally only support string values for the "default" property in your definitions - you have ... and later on ... If you remove default or give it a string value your definition loads ok. I'll follow up with the swagger team to see if I've understood this correctly. /Ole |
I go to http://editor.swagger.io and load the default example file. Then I download both spec.json and spec.yaml. When I try to create a new Project in SoapUI Pro by using the downloaded spec.json as Swagger Definition the import fails with
When I try to import spec.yaml instead, the import fails with
The swagger spec is version 2.0. I'm using SoapUI Pro 5.1.2 with soapui-swagger-plugin-0.3.1-plugin-dist installed.
The text was updated successfully, but these errors were encountered: