add operation ids

[joprice]

To enable code generation, swagger provides the 'operationId' field. This is expected to be unique, as the documentation for this field states:

Unique string used to identify the operation. The id MUST be unique among all operations described in the API. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is recommended to follow common programming naming conventions.

However, according to some comments here OAI/OpenAPI-Specification#381, this is only meant to be unique per endpoint, which should work for most use cases.

However, since I'm only using the method name this would cause issues if two controllers are used with the same method in the same routes file:

# for now, PUT and POST have the same behavior
PUT    /users    controllers.Users.add
POST /users    controllers.Users.add

We may want validation for a use case like that. We could also allow customization via a function passed to the generator like operationId: Route => String

[coveralls]

Coverage increased (+0.07%) to 90.942% when pulling 318b60d on joprice:operationIds into 8e377d3 on iheartradio:master.

[kailuowang]

👍