Partial template invocations should support content

[RyanMilligan]

When invoking a custom tag, it is possible to place content inside it which will then be rendered as part of the custom tag. Partial template invocations use the same basic mechanism as custom tags (renderer functions), so I would expect them to support it as well.

For example:

{{<test}}This is a partial! <b><content /></b>{{/test}}

{{>test}}And here is the content.{{/test}}

Currently, this throws a lot of internal null-ref exceptions, which suggests that the idea of providing content to a partial invocation simply hasn't been considered.

[justinbmeyer]

I think the issue here is that helpers (and tags) might not get passed down through these partials.

It would be cool if scope.templates or scope.content could access the underlying template or content and then just pass it to the partial.