Nested partial not processed

[lcsqlpete]

I have a situation where my main mustache template loads a partial and that partial loads a second partial.

The array passed to the main template includes the entries needed for the second partial but its code does not appear in the final output nor is there an error message. Ive checked all the obvious things like typos, file permissions, etc.

If I move the contents of the second partial into the first partial instead of loading the second partial, all works correctly.

I can't remember if I have attempted to do this in the past but I recently reorganized my partials template directory to contain a directory for each function within my website with all the partials for that function within it. My partials loader references my main partials directory and when I load a partial, it's in the form {{>directory/partial_name}}, not sure if that might cause this problem. All works fine with this structure when I load a partial directly from a main template, the problem only occurs when a partial loads another partial.

Any ideas what might be causing this?

[bobthecow]

I'm not sure I follow. Can you provide an example case so I can reproduce your issue?

[lcsqlpete]

I'm trying to get the code into a comment but it ends up being horribly fromatted. I click the <> icon to insert the code, is there some other way to format code correctly?

[bobthecow]

If you make a block with three backticks (`) on a line by themself, then your code, then three backticks after the last line, it'll be posted exactly as you enter it.

[lcsqlpete]

Got it.

…

On Thu, Aug 25, 2022 at 3:39 PM Justin Hileman ***@***.***> wrote: If you make a block with three backticks (`) on a line by themself, then your code, then three backticks after the last line, it'll be posted exactly as you enter it. — Reply to this email directly, view it on GitHub <#401 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACA2CFHKNCLEHLGEKPO42G3V27Y2RANCNFSM55ULWO6Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>