Jeremy Whitlock

Well, it's still a lot to type. I could potentially add `req.sway.getParam(name, [location])` that would basically be a shortcut for `req.sway.operation.getParameter(name, [location])`. Maybe shortcuts for all of the `Operation` methods...

What about making `req.sway` _the_ `Operation` object?

If I make `req.sway` the corresponding operation, that will work just fine. Now, just so you know, `Operation#getParameter` returns a `ParameterValue` and that itself has the following getters: - `error`:...

I think that's what I'm learning toward. Giving access to the Sway `Operation`, and by extension the rest of the Sway API, would let someone do more but making the...

Thanks for the feedback. I'll do my best to run with the feedback I have and get something solid out soon.

I agree. What if we allowed you to have options that would work something like this _(The example below is a simplified version of the default controller resolver and processor)_:...

I threw this together pretty quickly but I think if you can dictate what a controller is, and its name, and also dictate what route handlers are, that should handle...

What about doing away with `x-swagger-router-controller` and just use `operationId` for this? So instead of `x-swagger-router-controller: Users` and `operationId: getAllUsers`, we could have `operationId: Users#getAllUsers`? Since `operationId` must be unique,...

Good to hear. It seems we agree on how the route map gets generated, or provided, but do you have any opinions after that? How a Swagger operation is mapped...

Yes @confuser, that's the plan. To use `options.controllerProcessor` to be able to instantiate/prepare/... your controllers and their resulting route handlers.