Re: Any tools for generating a web form out of a model in the swagger spec?

2017-09-18 Thread Ron Ratovsky
We used to have that functionality in a previous version of swagger-ui. We’ll 
probably introduce it again, though it’s not high on our list at the moment.

Of course community contributions could help.

 

 

 

From:  on behalf of Renier Morales 

Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Monday, September 18, 2017 at 17:21
To: "swagger-swaggersocket@googlegroups.com" 

Subject: Re: Any tools for generating a web form out of a model in the swagger 
spec?

 

No, that does not create a form based on the model fields. It just provides a 
big text area so you can enter the model in whatever representation format is 
supported (e.g. JSON, XML). I'm was hoping for something that will render form 
fields, one for each field in the model, taking into account the type of each 
model field to provide the proper form field. 

 

-Renier

 

On Sep 15, 2017, at 5:53 AM, Ron Ratovsky  wrote:

 

https://github.com/swagger-api/swagger-ui ?

 

 

 

From:  on behalf of Renier Morales 

Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Friday, September 15, 2017 at 04:37
To: Swagger 
Subject: Any tools for generating a web form out of a model in the swagger spec?

 

Hi, 

 

Anyone knows of a tool to generate a form on the web out of a model in the 
swagger spec?

Seems to me there is enough information to tell which are the required fields, 
type, descriptions, etc. to generate a good form. Makes me think something like 
that must exist already somewhere.

 

Thx.

 

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


 

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "Swagger" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/swagger-swaggersocket/W6rtfPjelgI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

 

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to create a Swagger *.yaml or *.json definition file and project settings?

2017-09-18 Thread Vigfus A
Thank you for all the help Ron! It's now been converted into ReadyAPI.

For other people trying to do this with an old Swagger version.
Bring up the Swagger side in Chrome
Bring up the Development menu, go to Network tab and refresh it
Right click on your services and choose Copy->Copy link address
Paste the link into another Chrome tab + Enter
Copy all the content displayed in the browser window
Paste it into an editor like Notepad ++ and save it as a *.json
Open ReadyAPI, create a new project and import the the swagger definition 
(your newly saved *.json)
Rejoice :)



Den måndag 18 september 2017 kl. 11:28:03 UTC+2 skrev Ron:
>
> It looks like there might be something corrupt with the apidocs file 
> itself. Are you able to share it?
>
>  
>
>  
>
>  
>
> *From: * on behalf of 
> Vigfus A 
> *Reply-To: *"swagger-sw...@googlegroups.com " <
> swagger-sw...@googlegroups.com >
> *Date: *Monday, September 18, 2017 at 12:10
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> I saved the file and tried to import it to ReadyAPI. Unfortunately I got 
> an error (see attached file). Is there anything else I can do or should I 
> check with the guys over at ReadyAPI? 
>
>  
>
> Is it possible to upgrade to a newer version of the spec and still keep it 
> compatible?
>
>
>
> Den måndag 18 september 2017 kl. 10:33:59 UTC+2 skrev Ron: 
>
> Yup, that’s the file. Unfortunately, it’s an old version of the spec, 
> however I think SoapUI Pro would support it.
>
> Save that file locally and try importing it.
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Monday, September 18, 2017 at 11:22
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> There's no swagger.json, but in apidoc (see attached file) I found the 
> following rows. Would that be the one? 
>
>  
>
>1. {apiVersion: "1", swaggerVersion: "1.2",…} 
>
>
>1. apiVersion:"1"
>   2. apis:[{path: "/version", description: "Version av API"}, {path: 
>   "/admin", description: "Admin"},…]
>   3. swaggerVersion:"1.2"
>
>
> Den måndag 18 september 2017 kl. 09:26:17 UTC+2 skrev Ron: 
>
> No, unfortunately that’s not it.
>
>  
>
> It is most likely a file called ‘swagger.json’ or simply ‘apidocs’.
>
>  
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Monday, September 18, 2017 at 09:54
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> Good morning, 
>
>  
>
> I've looked through the Network tab and had a look in the swagger.js file 
> (see attached pic if it's the correct file).
>
> I came across two version notifications
>
> At the top this was commented
>
> // swagger.js
>
> // version 2.0.41
>
>  
>
> and then further down this code which felt a bit odd since a developer 
> just came by and said they were using version 1.3.6
>
> response: function (resp) {
>
>   var responseObj = resp.obj || JSON.parse(resp.data);
>
>   _this.swaggerVersion = responseObj.swaggerVersion;
>
>   if (_this.swaggerVersion === "1.2") {
>
> return _this.buildFromSpec(responseObj);
>
>   } else {
>
> return _this.buildFrom1_1Spec(responseObj);
>
>   }
>
> }
>
>
> Is that the information you need or should I look elsewhere?
>
>
>
> Den fredag 15 september 2017 kl. 20:34:53 UTC+2 skrev Ron: 
>
> Great, we’re making progress.
>
>  
>
> “Swagger” is the name of a set of open source project around the OpenAPI 
> specification.
>
> If you want to compare it to the SOAP days, the OpenAPI is to REST what 
> WSDL is to SOAP.
>
>  
>
> The screenshot you’re sharing is from swagger-ui, one of our tools. That 
> takes an OpenAPI specification and renders it.
>
>  
>
> The good news is that ‘xsd’ you’re looking for is hidden there. That would 
> also be the file you can load into SoapUI Pro.
>
> The bad news is that the swagger-ui version you’re using is very old and 
> it might make things a bit trickier (might not even be supported by SoapUI 
> Pro).
>
>  
>
> First thing first, lets try to find that swagger.json file.
>
>  
>
> Open the swagger-ui you have in your browser.
>
> Then, open your browser’s developer tools, go to the network tab, and 
> refresh the page.
>
> That will show you a list of calls to load the files used in the page.
>
> One of those files, that should be relatively up in the requests, would be 
> a ‘swagger.json’ file. You 

Re: Any tools for generating a web form out of a model in the swagger spec?

2017-09-18 Thread Renier Morales
No, that does not create a form based on the model fields. It just provides a 
big text area so you can enter the model in whatever representation format is 
supported (e.g. JSON, XML). I'm was hoping for something that will render form 
fields, one for each field in the model, taking into account the type of each 
model field to provide the proper form field.

-Renier

> On Sep 15, 2017, at 5:53 AM, Ron Ratovsky  wrote:
> 
> https://github.com/swagger-api/swagger-ui 
>  ?
>  
>  
>  
> From:  > on behalf of Renier Morales 
> >
> Reply-To: "swagger-swaggersocket@googlegroups.com 
> " 
>  >
> Date: Friday, September 15, 2017 at 04:37
> To: Swagger  >
> Subject: Any tools for generating a web form out of a model in the swagger 
> spec?
>  
> Hi, 
>  
> Anyone knows of a tool to generate a form on the web out of a model in the 
> swagger spec?
> Seems to me there is enough information to tell which are the required 
> fields, type, descriptions, etc. to generate a good form. Makes me think 
> something like that must exist already somewhere.
>  
> Thx.
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Swagger" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to swagger-swaggersocket+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Swagger" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/swagger-swaggersocket/W6rtfPjelgI/unsubscribe
>  
> .
> To unsubscribe from this group and all its topics, send an email to 
> swagger-swaggersocket+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to create a Swagger *.yaml or *.json definition file and project settings?

2017-09-18 Thread Ron Ratovsky
It looks like there might be something corrupt with the apidocs file itself. 
Are you able to share it?

 

 

 

From:  on behalf of Vigfus A 

Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Monday, September 18, 2017 at 12:10
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

I saved the file and tried to import it to ReadyAPI. Unfortunately I got an 
error (see attached file). Is there anything else I can do or should I check 
with the guys over at ReadyAPI? 

 

Is it possible to upgrade to a newer version of the spec and still keep it 
compatible?



Den måndag 18 september 2017 kl. 10:33:59 UTC+2 skrev Ron: 

Yup, that’s the file. Unfortunately, it’s an old version of the spec, however I 
think SoapUI Pro would support it.

Save that file locally and try importing it.

 

 

From:  on behalf of Vigfus A 
Reply-To: "swagger-sw...@googlegroups.com" 
Date: Monday, September 18, 2017 at 11:22
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

There's no swagger.json, but in apidoc (see attached file) I found the 
following rows. Would that be the one? 

 

{apiVersion: "1", swaggerVersion: "1.2",…} 
apiVersion:"1"
apis:[{path: "/version", description: "Version av API"}, {path: "/admin", 
description: "Admin"},…]
swaggerVersion:"1.2"
Den måndag 18 september 2017 kl. 09:26:17 UTC+2 skrev Ron: 

No, unfortunately that’s not it.

 

It is most likely a file called ‘swagger.json’ or simply ‘apidocs’.

 

 

 

From:  on behalf of Vigfus A 
Reply-To: "swagger-sw...@googlegroups.com" 
Date: Monday, September 18, 2017 at 09:54
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

Good morning, 

 

I've looked through the Network tab and had a look in the swagger.js file (see 
attached pic if it's the correct file).

I came across two version notifications

At the top this was commented

// swagger.js

// version 2.0.41

 

and then further down this code which felt a bit odd since a developer just 
came by and said they were using version 1.3.6

response: function (resp) {

  var responseObj = resp.obj || JSON.parse(resp.data);

  _this.swaggerVersion = responseObj.swaggerVersion;

  if (_this.swaggerVersion === "1.2") {

return _this.buildFromSpec(responseObj);

  } else {

return _this.buildFrom1_1Spec(responseObj);

  }

}


Is that the information you need or should I look elsewhere?



Den fredag 15 september 2017 kl. 20:34:53 UTC+2 skrev Ron: 

Great, we’re making progress.

 

“Swagger” is the name of a set of open source project around the OpenAPI 
specification.

If you want to compare it to the SOAP days, the OpenAPI is to REST what WSDL is 
to SOAP.

 

The screenshot you’re sharing is from swagger-ui, one of our tools. That takes 
an OpenAPI specification and renders it.

 

The good news is that ‘xsd’ you’re looking for is hidden there. That would also 
be the file you can load into SoapUI Pro.

The bad news is that the swagger-ui version you’re using is very old and it 
might make things a bit trickier (might not even be supported by SoapUI Pro).

 

First thing first, lets try to find that swagger.json file.

 

Open the swagger-ui you have in your browser.

Then, open your browser’s developer tools, go to the network tab, and refresh 
the page.

That will show you a list of calls to load the files used in the page.

One of those files, that should be relatively up in the requests, would be a 
‘swagger.json’ file. You can save it from there.

 

After you have the file, open it and look for either ‘swagger’ or 
‘swaggerVersion’ in it, and let me know the value of that field.

 

 

From:  on behalf of Vigfus A 
Reply-To: "swagger-sw...@googlegroups.com" 
Date: Friday, September 15, 2017 at 20:47
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

It might be my terminology that is off as I haven't used Swagger before, but 
there's an icon in the top left that looks like this  {...}  and links to 
swagger.wordnik.com. It might be a third party product that allows you to test 
your APIs and get simple responses. I was hoping I could get a file with the 
data shown in the pic below i.e. like the old XSD so I could import it into 
soapUI and soapUI would know what to expect if I call this API. In soapUI I 

Re: How to create a Swagger *.yaml or *.json definition file and project settings?

2017-09-18 Thread Vigfus A
I saved the file and tried to import it to ReadyAPI. Unfortunately I got an 
error (see attached file). Is there anything else I can do or should I 
check with the guys over at ReadyAPI?

Is it possible to upgrade to a newer version of the spec and still keep it 
compatible?


Den måndag 18 september 2017 kl. 10:33:59 UTC+2 skrev Ron:
>
> Yup, that’s the file. Unfortunately, it’s an old version of the spec, 
> however I think SoapUI Pro would support it.
>
> Save that file locally and try importing it.
>
>  
>
>  
>
> *From: * on behalf of 
> Vigfus A 
> *Reply-To: *"swagger-sw...@googlegroups.com " <
> swagger-sw...@googlegroups.com >
> *Date: *Monday, September 18, 2017 at 11:22
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> There's no swagger.json, but in apidoc (see attached file) I found the 
> following rows. Would that be the one? 
>
>  
>
>1. {apiVersion: "1", swaggerVersion: "1.2",…} 
>
>
>1. apiVersion:"1"
>   2. apis:[{path: "/version", description: "Version av API"}, {path: 
>   "/admin", description: "Admin"},…]
>   3. swaggerVersion:"1.2"
>
>
> Den måndag 18 september 2017 kl. 09:26:17 UTC+2 skrev Ron: 
>
> No, unfortunately that’s not it.
>
>  
>
> It is most likely a file called ‘swagger.json’ or simply ‘apidocs’.
>
>  
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Monday, September 18, 2017 at 09:54
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> Good morning, 
>
>  
>
> I've looked through the Network tab and had a look in the swagger.js file 
> (see attached pic if it's the correct file).
>
> I came across two version notifications
>
> At the top this was commented
>
> // swagger.js
>
> // version 2.0.41
>
>  
>
> and then further down this code which felt a bit odd since a developer 
> just came by and said they were using version 1.3.6
>
> response: function (resp) {
>
>   var responseObj = resp.obj || JSON.parse(resp.data);
>
>   _this.swaggerVersion = responseObj.swaggerVersion;
>
>   if (_this.swaggerVersion === "1.2") {
>
> return _this.buildFromSpec(responseObj);
>
>   } else {
>
> return _this.buildFrom1_1Spec(responseObj);
>
>   }
>
> }
>
>
> Is that the information you need or should I look elsewhere?
>
>
>
> Den fredag 15 september 2017 kl. 20:34:53 UTC+2 skrev Ron: 
>
> Great, we’re making progress.
>
>  
>
> “Swagger” is the name of a set of open source project around the OpenAPI 
> specification.
>
> If you want to compare it to the SOAP days, the OpenAPI is to REST what 
> WSDL is to SOAP.
>
>  
>
> The screenshot you’re sharing is from swagger-ui, one of our tools. That 
> takes an OpenAPI specification and renders it.
>
>  
>
> The good news is that ‘xsd’ you’re looking for is hidden there. That would 
> also be the file you can load into SoapUI Pro.
>
> The bad news is that the swagger-ui version you’re using is very old and 
> it might make things a bit trickier (might not even be supported by SoapUI 
> Pro).
>
>  
>
> First thing first, lets try to find that swagger.json file.
>
>  
>
> Open the swagger-ui you have in your browser.
>
> Then, open your browser’s developer tools, go to the network tab, and 
> refresh the page.
>
> That will show you a list of calls to load the files used in the page.
>
> One of those files, that should be relatively up in the requests, would be 
> a ‘swagger.json’ file. You can save it from there.
>
>  
>
> After you have the file, open it and look for either ‘swagger’ or 
> ‘swaggerVersion’ in it, and let me know the value of that field.
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Friday, September 15, 2017 at 20:47
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> It might be my terminology that is off as I haven't used Swagger before, 
> but there's an icon in the top left that looks like this  {...}  and links 
> to swagger.wordnik.com. It might be a third party product that allows you 
> to test your APIs and get simple responses. I was hoping I could get a file 
> with the data shown in the pic below i.e. like the old XSD so I could 
> import it into soapUI and soapUI would know what to expect if I call this 
> API. In soapUI I can build Test suites, Test cases and import data so I can 
> run a chain of tests whereas this interface only allows me to enter 

Re: How to create a Swagger *.yaml or *.json definition file and project settings?

2017-09-18 Thread Vigfus A
There's no swagger.json, but in apidoc (see attached file) I found the 
following rows. Would that be the one?


   1. {apiVersion: "1", swaggerVersion: "1.2",…}
  1. apiVersion:"1"
  2. apis:[{path: "/version", description: "Version av API"}, {path: 
  "/admin", description: "Admin"},…]
  3. swaggerVersion:"1.2"
   

Den måndag 18 september 2017 kl. 09:26:17 UTC+2 skrev Ron:
>
> No, unfortunately that’s not it.
>
>  
>
> It is most likely a file called ‘swagger.json’ or simply ‘apidocs’.
>
>  
>
>  
>
>  
>
> *From: * on behalf of 
> Vigfus A 
> *Reply-To: *"swagger-sw...@googlegroups.com " <
> swagger-sw...@googlegroups.com >
> *Date: *Monday, September 18, 2017 at 09:54
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> Good morning, 
>
>  
>
> I've looked through the Network tab and had a look in the swagger.js file 
> (see attached pic if it's the correct file).
>
> I came across two version notifications
>
> At the top this was commented
>
> // swagger.js
>
> // version 2.0.41
>
>  
>
> and then further down this code which felt a bit odd since a developer 
> just came by and said they were using version 1.3.6
>
> response: function (resp) {
>
>   var responseObj = resp.obj || JSON.parse(resp.data);
>
>   _this.swaggerVersion = responseObj.swaggerVersion;
>
>   if (_this.swaggerVersion === "1.2") {
>
> return _this.buildFromSpec(responseObj);
>
>   } else {
>
> return _this.buildFrom1_1Spec(responseObj);
>
>   }
>
> }
>
>
> Is that the information you need or should I look elsewhere?
>
>
>
> Den fredag 15 september 2017 kl. 20:34:53 UTC+2 skrev Ron: 
>
> Great, we’re making progress.
>
>  
>
> “Swagger” is the name of a set of open source project around the OpenAPI 
> specification.
>
> If you want to compare it to the SOAP days, the OpenAPI is to REST what 
> WSDL is to SOAP.
>
>  
>
> The screenshot you’re sharing is from swagger-ui, one of our tools. That 
> takes an OpenAPI specification and renders it.
>
>  
>
> The good news is that ‘xsd’ you’re looking for is hidden there. That would 
> also be the file you can load into SoapUI Pro.
>
> The bad news is that the swagger-ui version you’re using is very old and 
> it might make things a bit trickier (might not even be supported by SoapUI 
> Pro).
>
>  
>
> First thing first, lets try to find that swagger.json file.
>
>  
>
> Open the swagger-ui you have in your browser.
>
> Then, open your browser’s developer tools, go to the network tab, and 
> refresh the page.
>
> That will show you a list of calls to load the files used in the page.
>
> One of those files, that should be relatively up in the requests, would be 
> a ‘swagger.json’ file. You can save it from there.
>
>  
>
> After you have the file, open it and look for either ‘swagger’ or 
> ‘swaggerVersion’ in it, and let me know the value of that field.
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Friday, September 15, 2017 at 20:47
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> It might be my terminology that is off as I haven't used Swagger before, 
> but there's an icon in the top left that looks like this  {...}  and links 
> to swagger.wordnik.com. It might be a third party product that allows you 
> to test your APIs and get simple responses. I was hoping I could get a file 
> with the data shown in the pic below i.e. like the old XSD so I could 
> import it into soapUI and soapUI would know what to expect if I call this 
> API. In soapUI I can build Test suites, Test cases and import data so I can 
> run a chain of tests whereas this interface only allows me to enter data.
>
>  
>
> (In case the pic below doesn't show the model just shows the respons parm)
>
> parm 1 - string (optional)
>
> parm 2 - string (optional)
>
> parm 3 - string (optional)
>
> parm 4 - string (optional)
>
>
>
> Den fredag 15 september 2017 kl. 19:22:53 UTC+2 skrev Ron:
>
> Before diving into it more, can you explain:
>
>  
>
> There are around 10 different APIs that I can reach in Swagger
>
>  
>
> What is Swagger in that sentence?
>
>  
>
>  
>
>  
>
> *From: * on behalf of Vigfus A <
> vigf...@gmail.com>
> *Reply-To: *"swagger-sw...@googlegroups.com" <
> swagger-sw...@googlegroups.com>
> *Date: *Friday, September 15, 2017 at 19:16
> *To: *Swagger 
> *Subject: *Re: How to create a Swagger *.yaml or *.json definition file 
> and project settings?
>
>  
>
> There are around 10 different APIs that I can reach in Swagger, but I 
> can't see 

Re: How to create a Swagger *.yaml or *.json definition file and project settings?

2017-09-18 Thread Ron Ratovsky
No, unfortunately that’s not it.

 

It is most likely a file called ‘swagger.json’ or simply ‘apidocs’.

 

 

 

From:  on behalf of Vigfus A 

Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Monday, September 18, 2017 at 09:54
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

Good morning, 

 

I've looked through the Network tab and had a look in the swagger.js file (see 
attached pic if it's the correct file).

I came across two version notifications

At the top this was commented

// swagger.js

// version 2.0.41

 

and then further down this code which felt a bit odd since a developer just 
came by and said they were using version 1.3.6

response: function (resp) {

  var responseObj = resp.obj || JSON.parse(resp.data);

  _this.swaggerVersion = responseObj.swaggerVersion;

  if (_this.swaggerVersion === "1.2") {

return _this.buildFromSpec(responseObj);

  } else {

return _this.buildFrom1_1Spec(responseObj);

  }

}


Is that the information you need or should I look elsewhere?



Den fredag 15 september 2017 kl. 20:34:53 UTC+2 skrev Ron: 

Great, we’re making progress.

 

“Swagger” is the name of a set of open source project around the OpenAPI 
specification.

If you want to compare it to the SOAP days, the OpenAPI is to REST what WSDL is 
to SOAP.

 

The screenshot you’re sharing is from swagger-ui, one of our tools. That takes 
an OpenAPI specification and renders it.

 

The good news is that ‘xsd’ you’re looking for is hidden there. That would also 
be the file you can load into SoapUI Pro.

The bad news is that the swagger-ui version you’re using is very old and it 
might make things a bit trickier (might not even be supported by SoapUI Pro).

 

First thing first, lets try to find that swagger.json file.

 

Open the swagger-ui you have in your browser.

Then, open your browser’s developer tools, go to the network tab, and refresh 
the page.

That will show you a list of calls to load the files used in the page.

One of those files, that should be relatively up in the requests, would be a 
‘swagger.json’ file. You can save it from there.

 

After you have the file, open it and look for either ‘swagger’ or 
‘swaggerVersion’ in it, and let me know the value of that field.

 

 

From:  on behalf of Vigfus A 
Reply-To: "swagger-sw...@googlegroups.com" 
Date: Friday, September 15, 2017 at 20:47
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

It might be my terminology that is off as I haven't used Swagger before, but 
there's an icon in the top left that looks like this  {...}  and links to 
swagger.wordnik.com. It might be a third party product that allows you to test 
your APIs and get simple responses. I was hoping I could get a file with the 
data shown in the pic below i.e. like the old XSD so I could import it into 
soapUI and soapUI would know what to expect if I call this API. In soapUI I can 
build Test suites, Test cases and import data so I can run a chain of tests 
whereas this interface only allows me to enter data.

 

(In case the pic below doesn't show the model just shows the respons parm)

parm 1 - string (optional)

parm 2 - string (optional)

parm 3 - string (optional)

parm 4 - string (optional)



Den fredag 15 september 2017 kl. 19:22:53 UTC+2 skrev Ron:

Before diving into it more, can you explain:

 

There are around 10 different APIs that I can reach in Swagger

 

What is Swagger in that sentence?

 

 

 

From:  on behalf of Vigfus A 
Reply-To: "swagger-sw...@googlegroups.com" 
Date: Friday, September 15, 2017 at 19:16
To: Swagger 
Subject: Re: How to create a Swagger *.yaml or *.json definition file and 
project settings?

 

There are around 10 different APIs that I can reach in Swagger, but I can't see 
more than that the Response Content Type is "application/json; charset=UTF-8" 
together with Model/Model Schema. Last time I used APIs some 10 years ago we 
had XML and XSD, but I can see some resemblance between XSD and Model, but I 
can only see the response parms as information in Swagger. I've just assumed a 
Swagger definition sort of is like a XSD, but I can't that equivalent to the 
XSD file that I want to import to soapUI.

Not sure how big they are sizewise, but varies from a single parm to close to 
100 parms in the response.



Den fredag 15 september 2017 kl. 17:45:15 UTC+2 skrev Ron:

I assume you have an existing API.

 

Which language/library do you use to expose the 

Create New Project in Swagger

2017-09-18 Thread Palani Satheesh
i am working swagger editor  on docker by using following commands 
1.docker pull swaggerapi/swagger-editor.
2.docker run -p 80:8080 swaggerapi/swagger-editor

It working fine . now i want create new one how i do it.In editor file 
option doesn't have 
New and save option.how can i create new project.

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Authorization in the openAPI 3.0

2017-09-18 Thread Ron Ratovsky
It’s not yet supported.

 

See:

https://github.com/swagger-api/swagger-ui/issues/3641

https://github.com/swagger-api/swagger-ui/issues/3665

 

 

 

 

From:  on behalf of 
"maskalchuk.aliaksa...@gmail.com" 
Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Monday, September 18, 2017 at 09:49
To: Swagger 
Subject: Authorization in the openAPI 3.0

 

I'm trying to create an authorization in the openAPI 3.0, but I get the 
following problem: the authorization button just does not appear. Is this some 
kind of a bug?
I'm defined schema in the global components/securitySchemes section, as written 
in the specification, and then i applied them.
And another case - if i apply some random word in security - I don't have any 
error or smth.
I added screenshots and code.



-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Schema error

2017-09-18 Thread Ron Ratovsky
YAML is sensitive to indentation. 

>From what you shared it seems like a lot is misplaced or poorly indented. 

The error actually tells you which keywords cannot exist under the root, 
hinting you what’s not indented properly.

 

Another point – paths must begin with a ‘/’.

 

 

From:  on behalf of Olympacs 

Reply-To: "swagger-swaggersocket@googlegroups.com" 

Date: Saturday, September 16, 2017 at 03:04
To: Swagger 
Subject: Re: Schema error

 


I have just edited the entire code referring to the docs. I am still getting 
the errors. 

Errors
Hide
Schema error 
should NOT have additional properties
additionalProperty: get, datasets/{opec}, -in, database_code, type, required, 
description, responses:1, path, datasets/{opec}/{orb}
Jump to line 0
Schema error at paths
should be object
Jump to line 0
On Friday, September 15, 2017 at 6:03:33 AM UTC-4, Ron wrote: 

Hello,

 

The validation errors pretty much tell you what you’re doing wrong.

Please follow the documentation to learn about the structure of an API 
definition and take it from there.

https://swagger.io/docs/specification/2-0/basic-structure/

 

 

 

 

From:  on behalf of olympacs 

Reply-To: "swagger-sw...@googlegroups.com" 
Date: Thursday, September 14, 2017 at 22:21
To: Swagger 
Subject: Re: Schema error

 

I am attaching the code

On Thursday, September 14, 2017 at 3:20:54 PM UTC-4, Olympacs wrote: 

I am working on an existing api. Once it loads it shows a set of errors. I 
googled online but found similar errors when creating api's from scratch when 
you require path parameters. Please advise. 

Errors
Hide
Schema error 
should NOT have additional properties
additionalProperty: dataset
Jump to line 0
Schema error 
should have required property 'info'
missingProperty: info
Jump to line 0
Schema error 
should have required property 'paths'
missingProperty: paths
Jump to line 0
-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to swagger-swaggersocket+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.