Adding generic hooks doesn't have an effect on existing routes

[epaezrubio]

The following snippet will correctly print before hook followed by route handler:

router.hooks({
  before: (next) => {
    console.log('before hook');
    next();
  },
});

router.on('/', () => {
  console.log('route handler');
});

However, the following will just print route handler:

router.on('/', () => {
  console.log('route handler');
});

router.hooks({
  before: (next) => {
    console.log('before hook');
    next();
  },
});

Furthermore, if generic hooks are registered before and after route handlers are registered, then only the first routes will be affected by the global hooks.

Is this a design decision or a bug? It creates a complicated scenario, where the declarations need to be carefully called in the right order, and where you are limited by the initial declaration of the hooks. I can imagine many use cases where the library consumer would want to override the generic hooks.