Possible fix to template engines that attempt to copy the getter-laden context from going crazy

[dschissler]

Possible fix to template engines that attempt to copy the getter-laden context from going crazy

[cdaringe]

forgive my quick skim, but is calling model.serialize() into your template not an option or a solution?

[dschissler]

Its not desirably for me because I want to be able to access custom getters and methods on the model. In particular getting the name of a record/model is a lookup in a nedb database and I don't want to do that lazily because a small portion of the models will have a name and I also want to be able to call it with {{ model.name }} and to have that be a getter to all of the magic. I also want to be able to access DB specific "attributes" on the model by calling `{{ model.getAttr(...) }}.

I'm realizing that there is no hard standard for how a view is to interact with a template engine and so likely there will always be a necessity for a shim. One example is ampersand-view tries to call directly on the template with .call and in my case nunjucks is an object that should be called with render. So the native renderWithTemplate is inappropriate for me. In fact the parameters should be swapped since one always needs a template argument and the context is optional in the case of sending in a string.

[cdaringe]

if your lib needs pojo and some sort of clean/serialized content, most likely you will have to do some wrapping or proxying of your own. if you have an explicit suggestion on what &-view can do to help, please let us know