Skip to main content

JQuery Templates - too much recursion



I am using jquery templates to generate a tree structure to later display as a treeview of sections and items.





The structure of data looks like this, where each section has items and sections and each item can have more sections:







section

items

item

sections

item

sections

sections

section

sections

items



...and so on







My templates then recursively call each other:







<script id="my-item-tmpl" type="text/x-jquery-tmpl">

<li>

<span>${text}</span>

<ul>

{{each sections}}

{{tmpl($value) "sectionTmpl"}}

{{/each}}

</ul>

</li>

</script>



<script id="my-section-tmpl" type="text/x-jquery-tmpl">

<li>

<span>${text}</span>

<ul>

{{each items}}

{{tmpl($value) "itemTmpl"}}

{{/each}}



{{each sections}}

{{tmpl($value) "sectionTmpl"}}

{{/each}}

</ul>

</li>

</script>









$("#my-item-tmpl").template('itemTmpl');

$("#my-section-tmpl").template('sectionTmpl');





$.tmpl('sectionTmpl', { section }).appendTo(this);







I am finding however with around 4 levels into the structure I receive a "too much recursion " error in my console.





Is this just a limitation of the jQuery Template engine?





Edit:





I've resolved this by removing the {{each}} and replacing it with a {{tmpl}} call. The {{each}} was not needed. I have also wrapped each {{tmpl}} call in an {{if}} to ensure the collection exists.



Source: Tips4all

Comments

  1. Javascript has a recursion limit of about 1000 levels; with the structure you're using you probably shouldn't be hitting that, though.

    "My templates then recursively call each other"

    The markup makes my head hurt, so I'm having some difficulty reading the code (my problem, not yours), but any time I've hit the stack limit on recursion for anything, it has either been because I'm intentionally stressing something with deep recursion, or because I've got a circular reference somewhere so that my recursion never terminates.

    So, in general: make sure there's a way for your function to complete, instead of creating new instances of itself forever.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex