StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14797651
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-02-10T12:20:32.963
FavoriteCount
0
LastActivityDate
2013-02-10T12:20:32.963
LastEditDate
LastEditorUserId
0
OwnerUserId
1486467
ParentId
14793423
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>I think your "render" call in your BandsNewRoute is messing things up.Try making things go more with Ember defaults. So I would refactor your app to do this:</p> <p>(working fiddle: <a href="http://jsfiddle.net/andremalan/DVbUY/" rel="nofollow">http://jsfiddle.net/andremalan/DVbUY/</a>)</p> <p>Instead of making your own render, all you need to do is create a "bands" template (it can be completely empty except for {{outlet}} if you want) and a "bands.index" template.</p> <pre><code><script type="text/x-handlebars" data-template-name="application"> {{outlet}} </script> <script type="text/x-handlebars" data-template-name="bands/index"> <h2>Bands Index</h2> {{#linkTo bands.new}}New Band{{/linkTo}} </script> <script type="text/x-handlebars" data-template-name="bands"> <h1>Bands</h1> <p> {{#linkTo index}}Start Again{{/linkTo}} {{#linkTo bands.new}}New Band{{/linkTo}} </p> {{outlet}} </script> <script type="text/x-handlebars" data-template-name="bands/new"> I'm in new band! <a {{action "cancel"}}>Cancel</a> </script> </code></pre> <p>Your routes also clean up really nicely this way:</p> <pre><code>App.Router.map(function() { this.resource('bands', function() { this.route('new'); }); }); App.IndexRoute = Ember.Route.extend({ redirect: function() { this.transitionTo('bands'); } }); App.BandsNewController = Ember.Controller.extend({ cancel: function() { this.transitionTo('bands'); } }); </code></pre> <p>I hope that helps!</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEmber does not render after transition
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAndre Malan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEmber does not render after transition
  singulars
  PostTypePostTypeId
  PTQuestion
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
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COThanks, I tried your approach, I really like it. However, I've got this error: `Uncaught Error: assertion failed: an Ember.CollectionView's content must implement Ember.Array. You passed <(generated bands.index controller):ember279>`
  singulars
  PostPostId
  PO
  UserUserId
  USPavel S.
2. COOk, I figured out that the problem was caused by the fact I iterated over the objects which were supposed to be in the controller. However, when I excluded the `BandsIndexRoute` at all, there was no chance for Ember to guess my intentions and create that controller (filled by the data) for me. It works now and I thank you for your help!
  singulars
  PostPostId
  PO
  UserUserId
  USPavel S.

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.