Swagger-UI behaves erratically

[dothebart]

As discovered by Gareth Cox,
https://groups.google.com/forum/#!topic/arangodb/hdyn7ZrB4ms
This generated app :
https://docs.google.com/viewer?a=v&pid=forums&srcid=MDA1Njc3NDI0NzkxMDA3MjI4MDEBMDUwNjk4NTI2MzAwMzM1MjI3NjUBaGlCR2VhdklCLUVKATAuMQEBdjI&authuser=0

Will send an empty post body when trying to post to nodeTypes in the swagger UI:
{
"name": "Domain",
"description": "Domains",
"deleted": false
}
(reproduced with IceWeasel 31.6.0 from debian stable)
As the zip was produced on a mac, this may be related to #1368

[pluma]

That's amazing. I suspect this is an issue with Swagger 2.0 or the Swagger JSON generating code.

I doubt #1368 is related as that was not actually platform-specific and instead had to do with files not being included in the distribution packages of ArangoDB.

[fceller]

@pluma has this been fixed in 2.7.0?

[pluma]

@fceller I'm not sure. @dothebart Didn't you update Swagger as part of the API docs changes? Could you check whether this issue persists in devel?

[dothebart]

the generated swagger json: https://gist.github.com/60f6ca4cd0b38181d49e

The swagger editor shows several problems in the generated json.
The cause for the bug is, that several toplevel routes exist with the id 'post_' and thus it fails.
Swagger json generation has to be fixed.

/nodeTypes:
    post:
      tags:
        - /testbug
      summary: Creates a new nodeType.
      description: |

        Creates a new nodeType. The information has to be in the
        requestBody.
      operationId: post_  <- this id is not uniq - so the swagger json is broken.
      responses:
        default:
          description: undocumented body
          schema:
            properties: {}
            type: object
      parameters:
        - in: body
          name: nodeType
          description: The nodeType you want to create
          schema:
            $ref: '#/definitions/eY1IO57hkPlILIwm1HEZpWEFKpvteZ4D'

[dothebart]

the fixed file https://gist.github.com/pluma/5a0a62e11ee38e47bed9#file-swagger-json still reproduces this issue.