After doing a little digging, I believe I have found the problem. By using the syntax {>"{templateName}":data/}
, you are changing the context from root
to data
. When this happens, templateName
is no longer accessible when Dust tries to resolve the template name. So, Dust ends up searching for a template called ""
. I have filed an issue for this bug.
Having said that, if I were to write a book called "Dust: The Good Parts", I would leave contexts out of it (e.g. {#myData:myContext}
). I have found that they cause more problems than they solve.
As a workaround, you can use this syntax:
{templateName}
{>"{templateName}"/}
And then your "myTemplate" would need to do something like:
{data.one}
Here is an example of this working.