Router middleware to dispatch based on operationId

It would be nice to have a router middleware that would simplify the creation of handlers for methods based on the operationId.

The idea would be as follows.

Based on the following snippet

/pets:
    get:
      summary: List all pets
      operationId: listPets

one would create an object and use something like the following snippet to create the router.

var petrouter = {
    listPets: function(req, res, next) {
        // Do something
    }
};
app.use(middleware.router(petrouter));

Instead of having to the the following for ever method defined in the specification file

app.patch('/pets', function(req, res, next) { 
    // Do something
});

The advantage I see would be that the redundancy between what method to use (GET, PUT, …) and the exact path specification could be avoided. The only thing that maps between the swagger spec and the implementation is the operationId.

What do you think? Would this be a sensible enhancement?

[JonnyWaffles]

I too would like to know if this is a part of the swagger-express-middleware. The documentation is unclear as to how you bind operationId names to functions. The sample projects don’t see to even have js functions mapping the operationId in the YAML, so I’m not entirely sure how to wire any any of this up.

[nemani]

Is this a part of swagger-express-middleware or not?