fix next-connect integration

[beholderrk]

Condition with next

if (undefined !== next) {
    return next();
}

always triggered before handler. When next-connect used this behavior always return 404 status.

[sergioalvz]

Hey there! Thanks for contributing. I have been using this package with next-connect for a long time with no issue. Please, create a test case that helps to validate the change. They are under the tests/ folder.

[sualko]

@beholderrk I guess you are using this middleware like this:

connect().post(validate({ body: schema }, (req, res) => {
  // This function will be only executed if the incoming request complies
  // with the validation schema defined above.
})))

but you should not pass your handler to the validate function, instead you should pass your handler as second argument to the post function.

//.post( VALIDATE, HANDLER ) instead of .post( VALIDATE( HANDLER ))
connect().post(validate({ body: schema }), (req, res) => {
  // This function will be only executed if the incoming request complies
  // with the validation schema defined above.
}))

Therefore the precedence of the next call is irrelevant.

[beholderrk]

@sualko ok thx! I'll try this.