Something seems to be "eating" my locals!

[ghost]

I am passing them in but the ServerResponse.view.render() method eats them before I render!
This is a recent problem - this was not working wrong before the last week or so.

I managed to "patch" the view.render method to re-enable my locals but something in between where I'm saving them and where I'm re-inserting them is destroying the local variable namespace.

My patched version of the view.render method is at https://gist.github.com/781377#comments

[tj]

hmm, possibly the new res.local() merge is messing things up, tests and examples seem fine though, can you more info so I can reproduce?

[ghost]

The calling routine:

                        res.render('content/index.html', {
                            locals: {
                                foo: 'fooval',
                                contents: a,
                                form: form
                            }
                        });

The template:

Content Repositories

<% if (false && contents) { %>

<% for(var prop in contents){ var content = contents[prop]; %>

<%- content.name %>

<%- content.url %>

<%} %>

<% } else { %>

-- no content

<% } %>

Add Domain

<%- form.render() %>

Foo: <%- foo %>

[ghost]

(and for test purposes I erased all but the last line of the template)

As my gist demonstrates I validated that at the beginning of the view/render routine my local variables were present and by the time the code reached

//Attempt Render

my local variables were not evident.

I have not triangulated the part of http.ServerResponse.prototype.render that "eats" my locals but it is somewhere between those two points.

[tj]

hmm, the gist has code from master (2.x), but you use locals: {} ? from 1.x

[tj]

seems fine to me, closing for now