You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a parameter with type path that you leave blank, swagger-ui won't let you submit the request even if the parameter is optional.
For example I have a URI like this: http://foo.com/search/{query} and I might want search for everything using a blank query like this: http://foo.com/search/ but currently swagger won't let me submit that request (clicking the "Try it out!" button does nothing).
The text was updated successfully, but these errors were encountered:
You can certainly hack around in the swagger-ui, but in general, swagger wants path parameters to be required. For instance:
/foo/{bar}/search
/foo/search
If {bar} is omitted, the container would receive /foo//search which is interpreted as /foo/search in many server frameworks. To avoid the pitfalls of that, swagger says path parameters are required.
If you have a parameter with type
path
that you leave blank, swagger-ui won't let you submit the request even if the parameter is optional.For example I have a URI like this:
http://foo.com/search/{query}
and I might want search for everything using a blank query like this:http://foo.com/search/
but currently swagger won't let me submit that request (clicking the "Try it out!" button does nothing).The text was updated successfully, but these errors were encountered: