StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9548486
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-03-03T18:02:16.370
FavoriteCount
0
LastActivityDate
2012-03-03T18:02:16.370
LastEditDate
LastEditorUserId
0
OwnerUserId
1027004
ParentId
9544391
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p>With "mu is too short"'s advice. And a few crazy ideas I came up with an interesting approach to complex templating. *It almost works!</p> <p>So let's say I have this content (or data or view) which I want to put into a template:</p> <pre><code>var content = { title: "Black Book", girls: ["blonde", "brunette", "redhead"], digits: ['123', '456', '789'], calc: function () { return 2 + 4; } }; </code></pre> <p>And I have a template like this:</p> <pre><code><script type="text/template" id="template"> <h1>{{title}}</h1> <h3>{{calc}}</h3> <ul> <li><a href="{{digits}}">{{hair}}</a></li> </ul> </script> </code></pre> <p>And the end result I want is this:</p> <pre><code> <h1>Black Book</h1> <h3>6</h3> <ul> <li><a href="123">blonde</a></li> <li><a href="456">brunette</a></li> <li><a href="789">redhead</a></li> </ul> </code></pre> <p>The problem we'll encounter is that we have arrays (or lists) nested in our original content, and if we tried to Mustache.render(html, content) we'd end up with only one li item or a whole array within one href="" attribute. So sad...</p> <p>So he's the approach, pass through the template multiple times. The first time, pass through and replace the top level items, and adjust the template for the next pass through. The second time, adjust one of the lists, and adjust the template for the third pass through, etc for how ever many layers of content you have. Here's the new starting template:</p> <pre><code><script type="text/template" id="template"> <h1>{{title}}</h1> <h3>{{calc}}</h3> <ul> {{#hair}} {{#digits}} <li><a href="{{digits}}">{{hair}}</a></li> {{/digits}} {{/hair}} </ul> </script> </code></pre> <p>On the first pass through fill in the top level stuff, and change {{digits}} to {{.}}</p> <pre><code>$.each(content, function (index, value) { template2 = template.replace(/{{title}}/ig, content.title) .replace(/{{calc}}/ig, content.calc) .replace(/{{digits}}/ig, '{{.}}'); }); </code></pre> <p>Now you have this:</p> <pre><code> <h1>Black Book</h1> <h3>6</h3> <ul> {{#hair}} {{#digits}} <li><a href="{{.}}">{{hair}}</a></li> {{/digits}} {{/hair}} </ul> </code></pre> <p>On the next pass through we'll just call Mustache.render(template2, content.digits); and that should give us:</p> <pre><code> <h1>Black Book</h1> <h3>6</h3> <ul> {{#hair}} <li><a href="123">{{hair}}</a></li> <li><a href="456">{{hair}}</a></li> <li><a href="789">{{hair}}</a></li> {{/hair}} </ul> </code></pre> <p>And that's where my logic dies, haha. Any help thinking this through would rock! I'm thinking I could take out the {{hair}} block elements and just do a $.each pass through content.girls and stack .replace three times. Or I could try to start with lowest level of content, and work my way up. I dunno.</p> <p>All this basically leaves me wondering if there's some "logic-less" way for this kind of nesting or multiple pass throughs to be put into mustache does handlebars do it?</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMustache (or Handlebars) iterating over two lists
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCosta
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.