@sman wrote:
Trying to get a basic service definition working and it simply does now work. I can do a GET without any parameters but as soon as I try any GET with parameters nothing happens in API Docs when I press “execute”. I tried using your twilio example JSON and simplfied it down to just one path and still does not work. I looked in storage/logs/dreamfacory.log and there are no errors.
Not a very good first impression of this product unfortunately. I had high hopes but I really need service definitions and HTTP service in general to be solid and I don’t get that impression. I know service definition is just for API Docs but it’s still critical that works.
This is what I slimmed down the Twilio example to. Verified it works on http://editor.swagger.io/ which found some errors I had to change, again, not a good first impression when your swagger examples don’t even pass verification.
{ "swagger": "2.0", "info": { "title": "Twilio Account API", "description": "Twilio is a cloud communications Infrastructure as a Service(IaaS) company based in San Francisco, California. Twilio allows software developers to programmatically make and receive phone calls and send and receive text messages using its web service APIs. Twilio's services are accessed over HTTP and are billed based on usage.", "termsOfService": "https://www.twilio.com/legal/tos", "version": "2010-04-01" }, "host": "api.twilio.com", "basePath": "/2010-04-01", "schemes": [ "https" ], "produces": [ "application/json" ], "consumes": [ "application/json" ], "paths": { "/{AccountSid}.{format}": { "get": { "summary": "Get Account", "description": "GetAccount", "operationId": "getaccount", "parameters": [ { "required": true, "in": "path", "name": "AccountSid", "type": "string" }, { "required": true, "in": "path", "name": "format", "type": "string" } ], "responses": { "200": { "description": "OK" } }, } } }, "definitions": {}}
Posts: 2
Participants: 1