maybe pass pug flags down to the template render call?

[misterbrownlee]

I'm wanting my Hyper Text Markup Language to have some--pretty without having to write my own template js or hack the default template in node_modules. However, maybe nobody else wants this feature? I think I'll take a poke at it anyway, unless someone stops me.

Ultimately the opts have get passed down to topdoc-default-template, but having them get parsed out of .topdocrc would be the right thing, which is handled here, not the template. I don't see other flags that would make much sense, and I don't know if mucking with an array of flags is worth it... not for now anyway. At the least I can start with the thing I need (setPugPretty: true or something), and folks can pile on if they want other flags?

It could be simple I think... if (config.setPugPretty) ... and just hand off and extra arg to the renderer call here. It might make a little ugly if else, but I could maybe build the call params prior to the call to clean it up a little?

WDYT y'alls?

[GarthDB]

We could do a whole pug option object that is passed as an object called pugOptions

[misterbrownlee]

Yes. I wasn't sure how fancy we wanted to get and ultimately I had to write my own extension of the default template and can pass whatever I want myself. Your call, if you are keen I'm happy to tinker on this and make a pull request.