- Updated dependencies, base files, and editions using boundation
- Minimum required node version changed from
node: >=0.8tonode: >=10to keep up with mandatory ecosystem changes
- Updated base files using boundation
- Compiled with CoffeeScript v2
- Added support for multiple partial paths
- Thanks to pflannery for pull request #34 being based off his initial contribution
- Updated dependencies
- Updated base files
- Updated dependencies
- Minor improvements to make debugging easier
- Now supports multiple partial paths - Thanks to pflannery for pull request #14
- Fixed error reporting when a partial breaks (regression since always???)
- Partials now render inside the
renderDocumentevent, rather than any random time - Updated dependencies
- Template data is now sent with partial calls by default, and can be turned off by setting the first object you pass the the partial as
false, e.g.<%- @partial('hello', false, blah) %>- This has been documented quite thoroughly now in the README - This backwards compatibility break is due to the incredibly high amount of "user error" issues not sending the template data by default causes. In hindsight, it has become apparent to us that sacrificing docpad performance time for developer performance time and developer happiness is a far better trade. Caring about performance should come secondary to happiness. Not before it. - For those whom do care about performance, you should update all your existing partial calls to make use of the new firstfalseobject practice, or if you are too lazy setperformanceFirst: truein the plugin's configuration options.
- You can now customise the collection name via the
collectioNameoption - Updated some older docpad api conventions for their newer equilevants
- Updated for DocPad v6.46.2
- Updated for DocPad v6.46
- Fixed
Cannot call method 'match' of null
- Fixed cacheable partials (broke in v2.6.0)
- Fixed
???being outputted for empty partials (bug introduced in v2.6.0) - Closes issue #5 and pull request #6 thanks to Bob VanderClay and Bruno Héridet
- Partials now begin rendering as soon as we receive them
- Dependency upgrades
- Dependency upgrades
- Dependency upgrades
- DocPad v6.24.0 support
- Repackaged
- Dependency upgrades -
bal-utilfrom 1.15.x to ~1.16.8 -coffee-scriptfrom 1.4.x to ~1.4.0
- Removed the possibility of name collisions when storing partial info
- You can now cache a partial by setting
cacheable: truein the partial's meta data - Doing this will only render it once per (re)generation. Cache is cleared after each (re)generation.
- New way of doing partials - Should be faster - Should support watching better - Supports fuzzy matching
- Thanks to ashnur for issue #283
- Fixed memory leak (didn't clean up after generations, so regenerations would take longer and longer) - Fixes #335
@partialsignature now changed from@partial(name,data)to@partial(name,objs...)- If multiple objects are specified, they will be shallow-y merged into an empty object - This allows you to do things like@partial('blah',@,{blah:'blah'})to extend the partialblahwith the template data and some custom partial data
- Re-added markdown files to npm distribution as they are required for the npm website
- Moved the insertion of the partial template helper into the new
extendTemplateDataevent
- Fixed path exists warning
- Updated for DocPad 6.1
- Updated for DocPad v5.2
- Partials are now created with
createDocumentinstead ofcreatePartialwhich has been removed - Partials which aren't found will now throw a warning
- Updated for DocPad v5.0
- Fixed multiple partials on the same document bug
- Initial working version for Benjamin Lupton's Website