515 swagger missing

[robot-ranger]

Ok...so...

swagger-codegen appears to only consider the first element listed in "content" (see #515 (comment)).

I am making some concessions to get functional auto-generated swagger clients and also maintain as much existing functionality as possible. This is what I have come up with.

this new PR produces the following on each path listed in swagger:

"responses": {
  "200": {
    "description": "OK",
    "content": {
      "text/plain": {
        "schema": {
	  "type": "object"
        }
      }
    }
  }
}

with the above, the python version of the swagger client template-generates response_type='object' for each end point method. I have not tested other languages.

Without any special headers added, this results in the generated python client returning a byte string of the xml response doc.
With "Accept":"application/json" added to the headers, the generated python client smoothly returns a python dict.

IMO, I think this is the best approach for now. AFAIK this is the most minimal response definition and it gets us going with rapidly generated swagger clients.
In the future, we could consider adding schemas for at least the rest-specific portions of mtconnect such as MTConnectDevices/MTConnectStreams/MTConnectErrors and Header schemas.

I have tested:

• to verify the output of swagger.json shows the above for each endpoint
• swagger-codegen with a python generated client:
  • no added headers > returns byte string xml
  • "Accept":"application/xml" in headers > return byte string xml
  • "Accept":"application/json" in headers > returns python dict 👍