StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19600614
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-25T22:53:04
FavoriteCount
0
LastActivityDate
2013-10-25T22:53:04
LastEditDate
LastEditorUserId
0
OwnerUserId
506979
ParentId
19599890
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think figured your problem. 1. You got your example mixed up You are adding <code>'root'</code> to the <code>my-link-to-works</code> helper: <pre><code>{{#my-link-to-works 'root' widget.href}} </code></pre> and doing the unshift on the <code>my-link-to-fails</code> helper. So actually both examples are different. One has two arguments (ex: 'root' and '/widget/foo') and the other only has one (ex: '/widget/foo'). 2. Anyway, why does it work when the first argument is 'root'? The <a href="http://emberjs.com/api/classes/Ember.Handlebars.helpers.html#method_link-to" rel="nofollow">link-to helper</a> first argument must be a <code>routeName</code>. This helper can also receive a second argument <a href="http://emberjs.com/api/classes/Ember.Handlebars.helpers.html#toc_supplying-an-explicit-dynamic-segment-value" rel="nofollow">supplying an explicit dynamic segment value</a> which appends it's value to the resolved route. This was how your arguments were interpreted. If you check your example, the working links resolve to, for example, <code>#//widget/foo</code>. You may notice the two forward slashes there, which are a result of your resolved route <code>#/</code> + your segment value <code>/widget/foo</code>. 3. Solution? Use the link-to helper directly: <code>{{link-to 'widget' 'widget.href'}}</code> and remove the <code>/widget/</code> part from your href strings or do something like this: <a href="http://jsfiddle.net/tqFJ3/4/" rel="nofollow">http://jsfiddle.net/tqFJ3/4/</a> The helper: (this is the same as using <code>link-to</code> directly) <pre><code>Ember.Handlebars.registerHelper('my-link-to-works', function() { // Do extra stuff here... return Ember.Handlebars.helpers['link-to'].apply(this, arguments); }); </code></pre> Change your widgets href and leave only the dynamic segments: <pre><code>App.IndexRoute = Ember.Route.extend({ model : function() { return { widgets: [ { href: 'foo' }, { href: 'bar' }, { href: 'baz' } ] }; } }); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOverloading "link-to" helper in ember.js
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoão Teixeira
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. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.