Hi Chris,

If I understand this correctly, the include helper isn't necessary. Here is an explantation.

Partials as the Mustache Spec specify should propagate the caller context.

Also, since #94 is it even possible to switch the context to anything you want:

Examples:

  {{> partial}} same as {{> partial this}}

Or:

  {{> partial context}}

Or:

  {{> partial ../}}

So, unless I'm missing something include helper is just an alias for native partials, right?

Thanks

To be honest, I'm not sure about the use case with traversing up in the context, I just ported the test until I saw it didn't parse ;) My use case is only about providing static context data to a partial.

Our Example: We have breadcrumbs that we sometimes render on the server and sometimes on the client. The first two breadcrumbs are always "Home" and "Back". So if we did this:

{{#each breadcrumbs}}
  {{>breadcrumb}}
{{/each}}

we would have to make sure that the "home" and "back" items are in the template context on the server and the client, basically duplicating code. With the include, we could instead write this template:

{{breadcrumb title="Home" url="http://example.com/"}}
{{breadcrumb title="I don't know my browser has a back button" url="javascript:history.back()"}}
{{#each breadcrumbs}}
  {{>breadcrumb}}
{{/each}}

Which would keep those two links shared in the template.