Ember nested and non-nested resource

Can I have a resource both by itself (e.g. /trilink/new ) and nested (e.g. /sublink/1/trilink/new ) ?

by pjmorse

HTML

<script src="http://cdnjs.cloudflare.com/ajax/libs/handlebars.js/1.0.0/handlebars.min.js"></script>
<script src="http://builds.emberjs.com/canary/ember.js"></script>
<script src="http://builds.emberjs.com/canary/ember-data.js"></script>
<script type="text/x-handlebars">
    <h1>Ember Resource alone and nested</h1>
    <div class='links'>
        <ul>
            <li>{{#link-to 'mainlink'}}Home{{/link-to}}</li>
            <li>{{#link-to 'orders'}}Orders{{/link-to}} ({{#link-to 'orders.new' }}new{{/link-to}})</li>
            <li>{{#link-to 'users'}}Users{{/link-to}}</li>
        {{! This is the important one, below: why can't I use 'user.orders' as a route here? }}
            <ul>
                <li>{{#link-to 'orders'}}User orders{{/link-to}} ({{#link-to 'orders.new' }}new{{/link-to}})</li>
            </ul>
        </ul>
    </div>
    <div class='content'>{{outlet}}</div>
</script>

<script type='text/x-handlebars' data-template-name='mainlink'>
    {{outlet}}
</script>

<script type='text/x-handlebars' data-template-name='mainlink/index'>
    <h2>Start</h2>
</script>

<script type='text/x-handlebars' data-template-name='orders'>
    {{outlet}}
</script>

<script type='text/x-handlebars' data-template-name='orders/index'>
    <h2>Orders</h2>
    <p>Expected at order index route (/orders/)</p>
</script>

<script type='text/x-handlebars' data-template-name='orders/new'>
    <h2>New order</h2>
    <p>Expected at order new route (/orders/new)</p>
</script>

<script type='text/x-handlebars' data-template-name='User'>
    {{outlet}}
</script>

<script type='text/x-handlebars' data-template-name='users/index'>
    <h2>Users</h2>
    <p>Expected at /users/</p>
</script>

CSS

a {color:#666}
a.active {color:#FF0000}
.links {padding: 10px;background-color:#CCC;}
.content {padding: 10px;}

CoffeeScript

window.App = Ember.Application.create()

App.Router.map ->
    @resource 'mainlink', path: '/', ->
        @resource 'orders', path: '/orders', ->
            @route 'new'
        @resource 'users', path: '/users', ->
            @resource 'orders', path: '/orders', ->
                 @route 'new'