Syntax for using Hogan/Mustache partials?

[Justin Sheehy]

I've recently been playing around a lot in Docpad and seriously considering moving several of my projects over to it.
However, while I've been able to get partials in Eco working according to the examples, I have been unable to tweak the syntax around to get partials to work with Hogan.

I'd rather use Hogan than Eco, and would rather not run all of my layouts through both if I didn't have to.
Like I said, still pretty new to Docpad, and I know Hogan/Mustache handle partials a bit differently than others, so maybe I'm just missing something...

Could anyone tell me the proper setup/syntax I should be using, supposing Docpad can even actually utilize Hogan partials at the moment?
Thanks!

[Benjamin Lupton]

Happy to help :)

Can you elaborate on what specifically is going wrong? and/or post a code example? That'll really help, as otherwise I'm just shooting in the dark.

[Justin Sheehy]

Hmmm, maybe I'm just asking the wrong question.
Is Docpad's Partials Plugin only meant for being used with Eco?

Or is it supposed to allow partials of any other supported template language (like Hogan/Mustache/Handlebars) to be placed in src/partials and be loaded into a layout file?

-- Justin

[Narciso Jaramillo]

I had issues with using Jade for partials as well--they're getting included unrendered. Still trying to track down the problem.

nj

[Benjamin Lupton]

Can someone post a repo that I can fiddle with?

[Justin Sheehy]

Sure, here's my sandbox for these types of things.
https://github.com/systemexitzero/docpad-sandbox 
I cleared it out mostly so all it has is 2 or 3 files I was using to test out the handlebars/hogan/mustache partials.

[Benjamin Lupton]

Cool thanks.

Looks like this is the same issue as this one: https://github.com/bevry/docpad/issues/257

Still looking for a fix.

[Justin Sheehy]

Ah, indeed. 
I originally posted to this group because I thought it to be a problem on my end, not a bug with Docpad.
In that case, would you prefer the conversation is continued on the issue rather than here?

[Benjamin Lupton]

It's one of those gray areas. We should support this, however it is a question of can we. I'll look into this tomorrow and see what I can come up with. For the meantime you can use the workaround mentioned on that issue here: https://github.com/bevry/docpad/issues/257#issuecomment-6830362

[Pete Schirmer]

I was able to get this working with a handlebars helper function: (in docpad.coffee file) 

docpadConfig = {
  plugins:{

   handlebars:{

     helpers:{

       partial:(content, options) -> output = @partial(content, options)
     }

   }

 }

}

module.exports = docpadConfig

and then using markup like this in the document.html.hb to include the partial: 

{{partial 'my_partial_file.html'}}

[Benjamin Lupton]

Awesome work Pete. There is a pull request here which seems to have taken a different approach: https://github.com/docpad/docpad-plugin-handlebars/pull/1

Mind commenting on it before I merge it in? Cheers!

[Pete Schirmer]

It seems that does partials by including content defined in the docpad config (coffee/ whatever) which works fine. 

my version just exposes the partial plugin engine to the hb rendering engine.. so you can define the file partials externally.