Access to a the templating context object in global functions

Just like #109, It would be quite useful to have access to the render context object inside global functions.

A use case:

I have a CMS system and I need a function which returns the url for content. The code bellow should work, as it works if it were a filter.

env.addGlobal("urlFor", function (content) {
    return this.ctx.baseUrl + "/" + content.slug;
});

Thanks

[carljm]

In general, nunjucks doesn’t intend to support untrusted template authors. There are too many ways for a malicious template author to at the very least DoS the system.

That said, I’m not sure either why settings are stored on the context. Convenience maybe?

[valtido]

here is what the object looks like,

env                 :"development"
etag                :"weak"
etag fn             :wetag(body, encoding)
jsonp callback name :"callback"
query parser        :"extended"
query parser fn     :parseExtendedQueryString(str)
subdomain offset    :2
trust proxy         :false
trust proxy fn      :trustNone()
view                :NunjucksView(name, opts)
view engine         :"njk"
views               :"C:\Users\..\dev\views"
x-powered-by        :true

I was more focused, on the view method, they can serve a different view with a bit of hacking.

but what’s to say you leave that on, forget all about it, and one day nunjucks, decides to extend the settings object to include more sensitive information, the context should display the settings period (as a principal).

I mean security wise, you do not want to expose anything you have explicitly decide to do so.