Is there a reason we can not have nested routes?

21

I’m having the same issue here, and I’d love to get some guidance. I have a gist with information here. There are some additional attempts in the comments.

https://gist.github.com/commadelimited/6779774

The linkTo helper works when I linkTo the specified route:

{{#linkTo "interactions"}}Interactions{{/linkTo}}

But the API endpoint still gets called as /interactions instead of /accounts/64/interactions/

22

@commadelimited

I think you should write

this.resource(‘accounts.account’ to avoid namespace resetting

Social.Router.map(function() {

this.resource('accounts',  { path: '/accounts' }, function(){
    this.resource('accounts.account', { path: ':account_id'}, function(){
        this.resource('interactions', { path: 'interactions'});
    });
});

});

You could try Ember Inspector as it will provide you a clear picture of generated routes with their Urls

23

oh hey, look what just happened…

https://github.com/emberjs/ember.js/commit/91579428ee4f32d69b680f1e5b859d276aa81412

3 Likes