i mean that i'd like to change the config on a route
Ideally I want to authenticate, then convert the payload to JSON using xml2js or xml2obj-stream or somesuch, but it doesn't look like I have a hook into the gap between authentication and payload parsing
@cwatsonc you can find the invite link in the homepage of https://hapijs.com/
or the link directly : https://join.slack.com/t/hapihour/shared_invite/enQtMjM5Njk1NDgzNTY5LThmODkxODIzOTg5NjJjODFiYjcxZDMxMTAyMzBkZDk3MWY4MTFlNDAyMTU3MmUwMmM0Y2UwMjU3YjAwYjRkN2E
I am trying to get to a plugin based implementation and am struggling with the server.register() and server.dependency() methods. I am relatively new to Node.js and to Hapi.js as a framework. As I read the API documentation the server.register(array) should register the enumerated plugins in the order of the array. server.dependency(pluginNamesArray) should ensure that the plugin that expresses the dependency is ensured those dependencies have completed registry before the "self" registration attempt. My current strategy attempt fails on the server being started before the plugin registration completes.
Moving over to Hapi 17 / Hapi-mysql-2 our database instances are now accessed via req.server.mysql.pool[x] (or req.server.plugins.db.name). Is there a simple way to access these at the point that a route handler module is registered? We have a couple of routes that immediately access the database on registration
if I have repose.validation with Joi Schema, do I need to return a plain object, can I not just return a mongo document?
Yes you should look at https://hapijs.com/api#server.ext() and maybe that schema can help you too https://futurestud.io/files/hapi/hapi-v17-request-lifecycle.pdf
Sorry for the typo. @dankell As long you register your plugins with await you should be good to use them anywhere you have access to request
I have a question
as it's an hapi default
and yes you should be able to create a Boom before throwing it, you just can't use the
new keyword
I haven't been able to find anything related to Joi references not resolving in route config validation, so I thought I'd try and ask here.
config: {
validate: {
params: { id: Joi.string().valid(Joi.ref('$auth.credentials.sub')) }
}
},
I get
message: '"id" must be one of [context:auth.credentials.sub]',
Is this expected behaviour or am I going about it wrong? Thank you.
No, @jsmpereira is trying to use the context given to joi validation : https://github.com/hapijs/hapi/blob/master/API.md#-routeoptionsvalidateoptions