StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15008337
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-02-21T17:15:36.670
FavoriteCount
0
LastActivityDate
2013-02-21T17:15:36.670
LastEditDate
LastEditorUserId
0
OwnerUserId
1463681
ParentId
15000494
PostTypeId
2
Score
22
ViewCount
0
LastEditorDisplayName
text
Body
After having inspected the router object again, I don't see any property in there that will allow you to grab the last route. In pre 4 there was a property for the last route, but it was a difficult property to work with. My solution is therefore the same as it was in pre 4: I'd create my own mixin to handle the routes that you navigate into, and from that list of routes, you can get whatever route you're after: the current one, the last one, et cetera... jsFiddle here: <a href="http://jsfiddle.net/sMtNG/">http://jsfiddle.net/sMtNG/</a> Mixin The first thing to do is create the mixin that will allow us to push the routes into a <code>HistoryController</code>. We can do this by creating a <code>setupController</code> method which of course gets invoked every time you move into a route. <pre><code>App.HistoryMixin = Ember.Mixin.create({ setupController: function() { this.controllerFor('history').pushObject(this.get('routeName')); } }); </code></pre> We are pushing the route into the <code>HistoryController</code>. History Controller Since we're currently pushing the <code>routeName</code> into a non-existent <code>HistoryController</code>, we'll need to go ahead and create that, which is absolutely nothing special. <pre><code>App.HistoryController = Ember.ArrayController.extend(); </code></pre> Index Controller Since the <code>HistoryController</code> stores the list of routes we've navigated into, we'll need it accessible on other controllers, such as the <code>IndexController</code>, we'll therefore use <code>needs</code> to specify in which controller it should be accessible. <pre><code>App.ApplicationController = Ember.Controller.extend({ needs: ['history'] }); </code></pre> Implement Mixin We now have everything we need to keep a track of the routes, and so we'll specify that our routes need to implement this mixin. <pre><code>App.CatRoute = Ember.Route.extend(App.HistoryMixin); </code></pre> Template Last but not least, now that we have a <code>HistoryController</code> which our <code>IndexController</code> can access, and the mixin pushes each accessed route into the <code>HistoryController</code>, we can use our application view to output a list of the routes, and specify the last route. Of course in your case you'll need the last route minus one, but there's no sense in me doing everything! <pre><code><h1>Routes History ({{controllers.history.length}})</h1> <ul> <li>Last Route: {{controllers.history.lastObject}}</li> {{#each controllers.history}} <li>{{this}}</li> {{/each}} </ul> </code></pre> I hope this gets you onto the straight and narrow.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I get My previous route?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWildhoney
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I get My previous route?
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.