Is this project still maintained?

[zevero]

I love doT, but there has been no commit for over a year now.
There are 35 interesting pull request out there.
I myself would like to have some Object iterator built in.

Please @olado consider those pull request. Merge or close.
If you have no time for this project ... why not assign it to somebody else?

[vphantom]

I suspect someone will need to step up with a fork that will become the main focus of the active community...

[houd1ni]

Hi all! I've forked it and will work with PR every day/week and write something by myself sometimes, so consider to switch the fork.

About me: I work currently with mustache templates in my team and want to work with bullet-speed special-propose templates like this with a new project. (also, other micro and fastest libs for sandwich architecture) So, feel free to contribute and share.

https://github.com/houd1ni/doT

[jimmywarting]

@houd1ni If you are going to step up to the plate then we need to be able to report issues on your repo

[houd1ni]

@jimmywarting omg, they're closed by default. I've fixed it, can you check it out now? Huge thanx!

[fabiocbinbutter]

I made a CLI wrapper around doT so that it can be used for example in build processes. It's at https://github.com/fabiocbinbutter/dot-cli . I'd like to add it to the readme & main site, but I'm not sure right now who will maintain what..

[vphantom]

FYI if anyone's curious while we wait for DoT support, after debating whether to fork DoT for my own needs (including CLI), I ended up writing a subset from scratch as JSTC which I'm actively maintaining on NPM/GitHub, under MIT License. It has partials (done slightly differently), evaluation and interpolation, thus implicitly it also has conditionals and loops because JavaScript itself does. It has simple HTML encoding based on Mustache's escapeHtml(). It just doesn't have the arrays syntactic sugar. It's designed as a build-time compiler but can be used client-side.

It's only weakness is the lack of precision in error messages, because of the shortcuts involved (i.e. new Function() doesn't say where an error occurs), although it seems DoT faced similar challenges.

[epoberezkin]

I do believe that even in its current condition doT is the best thing out there, I've been using it for ages without any issues and its performance and size are unmatched by any other JS templating library.
Nevertheless, PRs need to be merged or closed and the issues need to be addressed.
I will be maintaining doT going forward. Additional tests and making test status visible (so if PRs fail them it's obvious too) is the first thing I am going to add.

[epoberezkin]

closing this now

[houd1ni]

Nice! If you have the access, I'm closing the branch.

[epoberezkin]

@houd1ni sure, thank you. Any time you can spend commenting/reviewing is appreciated, it would help. I was going through the tickets, there are several things that need addressing. Some of the simple things can be merged quickly, but most would require a major version change (such as whitespace stripping change and config extension - these seem to be leading by the number of issues/PRs).

[houd1ni]

Yeah, I see: you've done a great work!
Of course, I'll do.