res.locals is not by default accessible within the executing context

[ilyabreev]

Can't use i18n functions in vash view just like that:

@__("i18n_key")

Any workarounds?

[kirbysayshi]

What i18n functions are you trying to use? __() is not a standard JS API as far as I know.

[ilyabreev]

I am trying to use function __()

There is i18n module: https://github.com/mashpie/i18n-node

In ejs view i can use it like that:

<%= __('Hello') %>

but in vash view i need to access function __() through @model

@model.__('Hello')

Is using @model really necessary?

[kirbysayshi]

Vash doesn't have any knowledge of the locals property that i18n-node uses for ejs, so there isn't an easy way to expose something to every template as a free variable. I suppose you could also useWith (https://github.com/kirbysayshi/vash#vash-config-usewith), and then ensure that __() is attached to whatever you pass in to vash.

There's another option though. You could attach __ to vash.helpers.__, and then access it at html.__(). Or even something not as gross looking like vash.helpers.txt and then html.txt().

[ilyabreev]

Oh, thank you a lot, man! This is really cool tip.

I missed one important point though.
I am using vash with express and expecting that vash is express-compliant. I think that supporting a locals property for express (as in other template engines) may be a great feature.

[kirbysayshi]

I'll try to look into adding locals support via express, but don't have an estimate on when that might happen. I have to investigate a bit more into how they actually behave, but it's probably doable.

[joevolcano]

How can I use app.locals or functions added to the model I am passing to the render method?

[ilyabreev]

Any progress on this issue?