request.server._views in plugin

[futurechan]

I was calling request.server._views.render to render some html server-side, which was working great. Now I have moved this to a plugin, but I can't seem to find the right _views object. What am I missing?

Similarly, how do I access plugin.app from a handler declared within the plugin. https://github.com/spumko/hapi/blob/master/docs/Reference.md#pluginapp

[hueniverse]

First, don't call anything starting with an _ because it is not a supported API. I am likely to change those frequently. You should use the reply.view() method.

As for plugin.app, it is not accessible unless you use plugin.expose(). I like plugin.bind() best. in general, plugin.app is a place for the plugin to maintain its own state, but it is not as useful as the other options above.

[futurechan]

@hueniverse I'm not trying to return the rendered view in an http response. I am trying to build a simple email template service that accepts a json payload, renders the html, and sends out the email via an smtp server.

Is there a way to access the rendered html after reply.view() is invoked?

Regarding plugin.bind(), that's what I ended up using. However, I am wanting to pass my smtp service wrapper to a few plugins. plugin.app looked a little cleaner rather than picking it off the request object.

[futurechan]

@hueniverse Awesome!

By the way, in the case that my handler is in a different file, what's the best way to share the plugin. Right now, I have a setup method that is exported. I call that method and pass the plugin in. It's a little messy, but I'm not sure what else to do.

Also, request.server.render throws an expection stating request.server has no method render(). Similarly, I passed plugin to the module that contains my handler and used plugin.render(). I got the same error.

I am running hapi 6.4.

[futurechan]

@hueniverse Super sorry. I just saw the 6.5 in the commit. Do you know when npm will be updated?

[hueniverse]

@futurechan use plugin.bind()

[lock]

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.