You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/Users/rockbot/npm-inc/newww/node_modules/hoek/lib/index.js:669
throw arguments[1];
^
ValidationError: child "appendNext" fails because ["appendNext" must be a boolean]
at Object.exports.process (/Users/rockbot/npm-inc/newww/node_modules/hapi-auth-cookie/node_modules/joi/lib/errors.js:140:17)
at internals.Any._validateWithOptions (/Users/rockbot/npm-inc/newww/node_modules/hapi-auth-cookie/node_modules/joi/lib/any.js:642:25)
at root.validate (/Users/rockbot/npm-inc/newww/node_modules/hapi-auth-cookie/node_modules/joi/lib/index.js:102:23)
at Object.internals.implementation [as cookie] (/Users/rockbot/npm-inc/newww/node_modules/hapi-auth-cookie/lib/index.js:41:23)
at internals.Auth.strategy (/Users/rockbot/npm-inc/newww/node_modules/hapi/lib/auth.js:47:41)
at internals.Plugin._applyChild (/Users/rockbot/npm-inc/newww/node_modules/hapi/lib/plugin.js:449:19)
at Object.auth.strategy (/Users/rockbot/npm-inc/newww/node_modules/hapi/lib/plugin.js:61:65)
at /Users/rockbot/npm-inc/newww/server.js:90:15
at done (/Users/rockbot/npm-inc/newww/node_modules/hapi/node_modules/items/lib/index.js:30:25)
at Object.exports.register (/Users/rockbot/npm-inc/newww/node_modules/hapi-auth-cookie/lib/index.js:15:5)
at /Users/rockbot/npm-inc/newww/node_modules/hapi/lib/plugin.js:242:14
at iterate (/Users/rockbot/npm-inc/newww/node_modules/hapi/node_modules/items/lib/index.js:35:13)
at Object.exports.serial (/Users/rockbot/npm-inc/newww/node_modules/hapi/node_modules/items/lib/index.js:38:9)
at internals.Plugin.register (/Users/rockbot/npm-inc/newww/node_modules/hapi/lib/plugin.js:224:11)
at Object.<anonymous> (/Users/rockbot/npm-inc/newww/server.js:80:8)
at Module._compile (module.js:456:26)
Here's the code that we've written (worked fine with version 2.0.0):
Reading the readme of the 2.0.0, it already expected a boolean. I think 2.1.0 is more strict about its input, so what was truthy before ('done') is not enough now, I'm not sure I'd qualify this as breaking.
This looks like an unintentional breaking change. The previous readme says Set to a string to use a different parameter name This is a feature that was removed. We should likely make the validation more relaxed to support this previous feature. We also need a test for this condition :)
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
Received this error:
Here's the code that we've written (worked fine with version 2.0.0):
Sidenote: if this was a purposeful, breaking change, the community would expect the version to be bumped to 3.0.0, not 2.1.0.
The text was updated successfully, but these errors were encountered: