Jonathan Vanasco

Years ago, I started work on extending ashes to track the utilized fields. I never got it to recurse correctly though. The use-case for me was to build a model...

Just a quick warning that you probably already are thinking of, but I'll state just I case... Ashes is very easy to extend as mentioned above, however you should be...

The hardcoding is (likely) because the dust specification is for curly braces. I don't know if @mahmoud would be open to this or not... But this is quite a fundamental...

On Jun 29, 2015, at 7:09 PM, Mahmoud Hashemi wrote: > From my perspective, Dust is a language and dust.js is a reference implementation. In spite of the docs, the...

Just saw this in the issues list. I had actually done this several months before -- https://github.com/mahmoud/ashes/wiki/Compatibility-with-LinkedIn-Dust.JS-Fork

oh there is also a `Compatibility` file that was pulled into trunk from a PR I made a while back -- https://github.com/mahmoud/ashes/blob/master/COMPATIBILITY.md

Thanks for migrating this. I didn't want to open up another ticket, since it was mentioned elsewhere. I think just showing the current rendering context/model is all that's needed. However,...

I would utilize functionality like that too, but you will need to fork this project to provide it. The explicit design of this project is to isolate every domain with...

In Cloudflare, I have 2 records: | type | name | content | | ---- | ---- | ---- | | NS | acme-dns | ns.acme-dns.example.com | | A |...

Here is the read me at an earlier version, which uses these names and has descriptions : https://github.com/joohoi/acme-dns/blob/0991b3e3c9f1dc56c596e05af149820c02bfd89e/README.md It was changed to the new names for clarity, but I find...