Bugfix: Template information not stored in correct scope

[jscharlach]

If EmailTemplate was used to render multiple different templates in rapid succession it would always use the last template called for every render. This update moves the non-static data into a scope object.

[jasonsims]

@jscharlach thanks for this! I think this actually relates to #46 that we were unable to reproduce. It looks like the scope changes broke the test for batch emails though. Can you fix the broken build as part of this PR?

[niftylettuce]

@jscharlach can you fix the broken build? /cc @jasonsims

[niftylettuce]

@jscharlach any luck?

[jscharlach]

Gah. These messages got stuck in my spam folder somehow. I'll take a look
tomorrow.

Sorry for the delay.
On May 27, 2014 12:50 PM, "Nick Baugh" notifications@github.com wrote:

@jscharlach https://github.com/jscharlach any luck?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/60#issuecomment-44302833
.

[jscharlach]

I've fixed the issue that I caused with batch template processing and slightly refactored my changes.

[jasonsims]

Thanks @jscharlach! The tests are still failing but only for node v0.8. Since we're dropping support that version anyway I'll include this in the v1.0 branch before merging it to master.

[jasonsims]

This is now merged into v1.0.0 and has been published to npm