StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POEmber.js Dynamic segment not working
primarykey
Id
18706005
data
AcceptedAnswerId
18734729
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-09T19:59:03.930
FavoriteCount
1
LastActivityDate
2013-09-11T07:04:42.303
LastEditDate
2013-09-10T07:35:04.440
LastEditorUserId
2074006
OwnerUserId
2074006
ParentId
0
PostTypeId
1
Score
1
ViewCount
956
LastEditorDisplayName
text
Body
I'm using Ember 1.0.0 and the latest build of Ember Data (beta), and I have a route with a dynamic segment that isn't working. I have defined the routes below: <pre><code>PwdMgr.Router.map(function() { this.resource("passwords", function(){ this.resource("password", {path: "/:password_id"}, function(){ this.route("edit"); }); }); } </code></pre> In the template passwords.index I display a list of models like this: <pre><code>{{#each}} <tr> <td>{{id}}</td> <td>{{name}}</td> <td>{{client.name}}</td> <td>{{service.name}}</td> <td>{{localisation.name}}</td> <td>{{status.name}}</td> <td>{{login}}</td> <td>{{password}}</td> <td> {{#link-to 'password.index' this}}{{/link-to}} {{#link-to 'password.edit' this}}{{/link-to}} </td> </tr> {{/each}} </code></pre> I have two links, one that goes to the route password.index and one to the route passwword.edit. I provide the model for the dynamic segment and the handlebars creates the URL correctly (/passwords/1 and /passwords/1/edit). My problem is that when I get to the URL /password/1 (or /password/1/edit), the model is not a single object but an array of objects. Since I'm using the default pattern, as explained in the guides, I didn't setup Route objects. But for debugging purposes I created a route object for the password.index route. Here's what it looks like: <pre><code>PwdMgr.PasswordIndexRoute = Ember.Route.extend({ model: function(params){ console.log(params); return this.get('store').find('password',params.password_id); }, setupController: function(controller, model){ console.log(model); } </code></pre> }); And here's my console log: <pre><code>Object {} app.js (line 31) <DS.RecordArray:ember435> { content=[3], store=<DS.Store:ember506>, isLoaded=true, more...} app.js (line 35) </code></pre> The empty object explains why I get an array of object but is there a reason why the params variable is an empty object? Thanks a lot [EDIT] I have changed my Router.map like so: <pre><code>PwdMgr.Router.map(function() { this.resource("passwords", function(){ this.route("detail", {path: "/:password_id"}); this.route("edit", {path: "/:password_id/edit"}); }); }): </code></pre> And the dynamic segment for both "detail" and "edit" routes works fine. I think the problem comes from the fact that the dynamic segment is in the nested resource, which is strange because the Emberjs guides' examples are with dynamic segments in nested resources.
Tags
<javascript><ember.js><ember-data><handlebars.js>
Title
Ember.js Dynamic segment not working
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USSimon Cateau
UserOwnerUserId
1. USSimon Cateau
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POEmber.js Dynamic segment not working
 UserUserId
 USafroglasses
 VoteTypeVoteTypeId
 VTFavorite
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.