Dear {{name}}, {{> mypartial}}
\r\n```\r\nAnd another template (defined in `mypartial.hogan`):\r\n```\r\n{{text}}\r\n```\r\nAssuming you use a `grunt-hogan` target to compile both these templates into a single module, you end up with a template render object something like:\r\n```javascript\r\n{\r\n message: func(...){...},\r\n mypartial: func(...){...}\r\n}\r\n```\r\nWe want Hogan to now expand the `mypartial` template and interpret the `message` template as:\r\n```\r\nDear {{name}}, {{text}}
\r\n```\r\nBut how do we give Hogan what it needs to resolve the `mypartial` template? `grunt-hogan` supports this through three features:\r\n### 1. \"Sibling\" Partial Templates\r\nBy default, if you call the render function with just a context object:\r\n```javascript\r\ntemplate.message({name:'Hulk', text:'Have a nice day!'});\r\n```\r\n`grunt-hogan` will make the `mypartial` template available to the `message` template *automatically*. \r\nThis will happen if:\r\n\r\n 1. `message.hogan` and `mypartial.hogan` were bound together into a single template render module\r\n 2. The `nameFunc` (if specified) preserves the partial name `mypartial` mentioned in the `message.hogan` template\r\n\r\nSince `grunt-hogan` exposes the render as a function, this is the intended \"common practice\" for partial templates. \r\n\r\n*If you want a partial template to be automatically available, bind it as a sibling template with the template that depends on it.*\r\n\r\n### 2. Explicit Partial Templates\r\nTo disable the default behavior of \"Sibling\" Partial Templates, you simply specify the second parameter:\r\n```javascript\r\ntemplate.message(\r\n {name:'Hulk', text:'Have a nice day!'}, //context\r\n {mypartial: getMyPartialFromSomewhere()} //partials\r\n );\r\n```\r\nBut now you are on your own when resolving the `Hogan.Template` objects passed through to the Hogan render. Hogan will use the passed partials only if they are valid `Hogan.Template` instances.\r\n### 3. Use the `exposeTemplates` task option\r\nIf you don't know at template compile time what partials are needed, \r\nand/or can't/won't put templates together as \"Siblings\", then you will need a way to retrieve the actual \r\n`Hogan.Template` instances from `grunt-hogan` modules. \r\nTo do this, specify the `exposeTemplates` option on the compile task. \r\nDoing so makes the actual templates available as a `template` property on the module:\r\n```javascript\r\n{\r\n message: func(...){...},\r\n mypartial: func(...){...},\r\n templates: { message: {...}, mypartial: {...}}\r\n}\r\n```\r\nUsing this, you can pass the actual `Hogan.Template` instance to wherever it is needed (with the \"Explicit Partial Templates\" mentioned above, for example).\r\n## Examples\r\n * See [an example gruntfile](example/Gruntfile.js)\r\n\r\n## Contributing\r\nIn lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using [grunt][grunt].\r\n\r\n## Release History\r\n * 0.3.1 - Updated the way grunt is specified in the `peerDependencies`\r\n * 0.3.0 - Improved grunt support\r\n * Switched to lodash\r\n * Upgraded hogan.js version\r\n * Added CI build and testings\r\n * Improved examples, and CI makes sure they work\r\n * 0.2.2 - Binder template overhaul\r\n * Added partial support on render functions\r\n * Sibling partials by default\r\n * *Breaking changes for precompiled template API*\r\n * 0.2.1 - AMD Binder\r\n * Now supports use of \"sibling templates\" (defined within the same binder) as partials\r\n * *Breaking change* - Now exports a render function instead of the full template\r\n * 0.1.1 - [*Breaking Changes* and Custom Binder Support](https://github.com/automatonic/grunt-hogan/issues?milestone=1)\r\n * \"render\" directive has [been discarded](https://github.com/automatonic/grunt-hogan/issues/8)\r\n * \"options\" notation has been discarded (supply attributes directly as keys on the target)\r\n\r\n##Acknowledgements\r\n * a comment by \"baz\" [here](http://soenkerohde.com/2012/02/node-js-server-side-compile-hogan-js-templates/) pointed me in the right direction\r\n\r\n## License\r\nCopyright (c) 2014 Elliott B. Edwards \r\nLicensed under the MIT license.\r\n\r\n[grunt]: http://gruntjs.com/\r\n[getting_started]: https://github.com/gruntjs/grunt/wiki/Getting-started\r\n","maintainers":[{"email":"elliott.b.edwards@gmail.com","name":"el2iot2"}],"time":{"modified":"2022-06-18T15:09:20.594Z","created":"2012-10-26T02:15:56.878Z","0.1.0":"2012-10-26T02:15:57.499Z","0.1.0-1":"2012-11-23T06:01:59.082Z","0.1.0-2":"2012-12-06T01:11:10.766Z","0.1.0-3":"2012-12-07T02:39:17.441Z","0.1.0-4":"2013-01-29T03:53:09.386Z","0.1.1-0":"2013-02-08T03:25:21.246Z","0.1.1-1":"2013-02-10T19:43:19.761Z","0.1.1-2":"2013-02-10T21:35:44.372Z","0.1.1-3":"2013-02-10T22:26:01.685Z","0.1.1-4":"2013-02-16T01:17:54.227Z","0.2.0":"2013-02-16T02:26:19.496Z","0.2.0-1":"2013-02-16T03:29:09.751Z","0.2.1-0":"2013-02-26T00:29:19.356Z","0.2.2-0":"2013-02-28T05:37:22.096Z","0.2.2-1":"2013-02-28T06:32:53.107Z","0.2.2-2":"2013-02-28T06:38:34.105Z","0.3.0":"2014-07-08T04:38:00.435Z","0.3.1":"2016-10-27T02:37:57.156Z"},"author":{"name":"Elliott B. Edwards","email":"elliott@automatonic.net","url":"http://automatonic.net"},"repository":{"type":"git","url":"git://github.com/automatonic/grunt-hogan.git"},"homepage":"https://github.com/automatonic/grunt-hogan","keywords":["gruntplugin","hogan.js","template","mustache","templating"],"bugs":{"url":"https://github.com/automatonic/grunt-hogan/issues"},"readmeFilename":"README.md"}