I am having difficulty with my securityDefinitions object.
My folder structure is like this:
/api
/console
/swagger
/file1.json
/file2.json
/swagger-ui
We are not yet ready to make the console (or associated swagger files)
available to the whole internet, so everything under /consol
>
>
>
>
>
> *From: *> on behalf of
> Andrew Campbell >
> *Reply-To: *"swagger-sw...@googlegroups.com " <
> swagger-sw...@googlegroups.com >
> *Date: *Wednesday, 3 August 2016 at 09:09
> *To: *Swagger >
> *Subject: *Mult
Can field names be editable in Swagger UI?
The curl to upload a file to my API looks something like this:
curl -i -X POST \
-H "Authorization: $AUTH" \
-H "Accept: application/json" \
-H "Content-Type: multipart/form-data" \
-F "$CHECKSUM=@$FILE" \
$HOST/api/fileupload
The problem is the -F "$CH
Just tried grabbing the latest version from Git. Same problem.
I've also tried reversing the order of the apiKey and Basic authorizations
- again, the same problem. When assembling the curl command, Swagger UI
seems to favour the basic authentication.
>
--
You received this message because yo
In that case I think the sweet spot is for me to provide a file with a
known checksum and hard code that into the swagger; that will work well
enough for our current purposes. At some point in the future I might hack
Swagger UI to see if I can make a field name editable.
>
>
--
You received th
I've created a cut-down version of the spec that displays the problem.
There is only one operation. When I login using both authorizations and
click "Try it out", this is the curl that the console generates
curl -X GET --header 'Accept: application/json' --header 'Authorization: Basic
c3dhZ2dlc
Just as a footnote to this. I have changed my configuration so I don't need
to use basic authorization any more. However, I'm still intrigued by this
problem and will work to help fix it.
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsubscri
I am having a caching issue.
I upload my swagger to the server, and view it in Swagger UI.
Then I change the swagger and re-upload it. Sometimes all I have to do to
see the changes is click the "Explore" button. Other times, I have to
refresh the entire Swagger UI. And occasionally the old swag
I've found a partial solution to this problem: when refreshing, strip
everything after the #! off the URI.
For example, if your current URI is
http://example.com/swagger-ui/#!/My_APIs/my_test_api, go to
http://example.com/swagger-ui/ and then refresh. That seems to have fixed
most of my proble
I am having real trouble with my accept headers.
I have two Swagger files. The only difference is one has
"host": "example.com"
And the other has
"host": "my.actual.domain"
When I use the example.com version, the value of the accept header is set
correctly.
When I use the version with m
Thanks.
Disabling caching made a difference, but once I added my API key via the
Authorize button, text/plain was back in the Accept header.
I'm being driven nuts by this, so I am stepping away from it for now. I
will post an update tomorrow, not least because someone else might have the
same
I disabled caching, turned my computer off, and went home. When I came
back, the issue seems to have been resolved :)
For future reference, I'm using Google Chrome on OS X. To disable caching:
Click the menu button (a vertical row of three dots).
Select More Tools > Developer tools. The dev to
I'm getting in my Example Values in Swagger UI.
For example
The model looks like this
Comments {
comment (Array[Comment], optional)
}
Comment {
id (string,null):
http://www.w3.org/TR/xmlschema-2/#string
}
I have attached a sample Swagger file that displays the problem.
I just can't
Thanks; I understand that the spec is invalid.
Can you tell me how to fix my spec? I've been trying, but can't seem to
find a solution.
>
>
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsubscribe from this group and stop receiving emails fro
Thanks. I've used http://bigstickcarpet.com/swagger-parser/www/index.html
to find the validation issues with my spec, and I have altered it so it is
now valid, at least according to that validator.
I'm still getting the same problem, and I could really use some help in
getting this fixed.
Upda
Thank you!
The problem was the missing "type": "string". This was further obfuscated
by a typo in the full 13k line spec; I wouldn't have found either of those
problems without your help.
>
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsub
Hi,
I'm getting infinite loops in my Swagger UI example values.
As you can guess from the name, I'm trying to describe a filesystem folder,
which can contain other folders (example Swagger attached).
I'd prefer not to have the infinite loop message. Can anyone point me in
the right di
Done - https://github.com/swagger-api/swagger-ui/issues/2417
--
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 m
18 matches
Mail list logo