This is the setup that I have
DS.RESTAdapter.configure 'plurals',
child: 'children'
App.Router.map ->
#resource 'people', ->
#resource 'person', path: ':person_id', ->
#route 'children'
App.PerosnChidlrenRoute = Ember.Route.extend
model: -> App.PerosnChidlren.find()
So, there is two problems here: first is that PersonChildren hitting /person_childrens instead of /people/:person_id/children.
And the second is incorrect pluralization as you can mention:)
Can you please explain how do I setup routing and pluralization correctly?
p.s. I've tried to put everything up in http://jsfiddle.net/UJkn3/1/
Related
I'm building an office reception app in Ember. When a person arrives at the office, they pop open the app and are taken through a three step wizard:
Choose a reason for visiting
Choose the person you've come to see
Confirm
The app also allows an administrator to view all of the visits and to view an individual visit.
I have Visit and Person models I've hooked up to a server using Ember Data. Here's what my routes look like:
App.Router.map () ->
#resource 'visits', ->
#resource 'visit', { path: '/:visit_id' }
#resource 'new', ->
#route 'welcome'
#route 'directory'
#route 'thanks'
This allows me to create a new Visit model in the VisitsNewRoute and use it in the welcome, directory and thanks views.
This works. However, it feels wrong to have a new resource, especially since it's conceivable I'll want at least one more new route in my application.
Is there a better way to do this?
I think that you can change the new resource to newVisit like this:
App.Router.map () ->
#resource 'visits', ->
#resource 'visit', { path: '/:visit_id' }
#resource 'newVisit', ->
#route 'welcome'
#route 'directory'
#route 'thanks'
Now you will have a NewVisitRoute where you can create a new Visit model to use in each of the child routes.
And you will be able to make a transition to this routes with the route names: newVisit.welcome, newVisit.directory and newVisit.thanks. You can use this route names in a link-to helper link this:
{{link-to "Welcome", "newVisit.welcome"}}
The recommended practice is to use a create/new route under the resource type, so new under visits, then `transitionTo('visit.welcome', newRecord). (I'm saying all of this with the assumption that welcome, directory, and thanks aren't part of the new record creation).
App.Router.map () ->
#resource 'visits', ->
#route 'new'
#resource 'visit', { path: '/:visit_id' }
#route 'welcome'
#route 'directory'
#route 'thanks'
Ember doesn't always name routes the way you want when dealing with routes nested more than one level. I would name your 'new' route as follows:
#resource 'visits.new', path: 'new', ->
There are a number of approaches you can use to structuring your routes depending on how you assign model ids and whether or not you are using localStorage to preserve user edits until they are persisted to the server.
I have my route pattern as follows:
App.Router.map () ->
#resource 'visits', ->
#route 'new'
#route 'crud', path: ':visit_id'
My 'new' routes create a new resource in the routes model callback which in my models auto-generates a v4 UUID. The new route then performs a transitionTo the crud route in the afterModel callback. In effect the 'visits.new' route acts as a trampoline and allows you to easily use {{link-to 'visits.new'}} from templates/menus etc.
The above approach allows you to to have a single crud route and crud controller that can handle all the show/create/update/delete actions for the model. The models isNew property can be used within your templates to handle any differences between create and update.
I also use localStorage so that newly created (but not yet persisted) models survive a browser refresh, the UUIDs really come in handy for both this and for persisting complex model graphs.
The above router pattern occurs quite a lot in my app so I have defined some base Route classes and a route class builder but the general pattern is as follows:
If using UUIDs:
App.VisitsNewRoute = Em.Route.extend
model: (params, transition)->
App.Visit.create(params)
afterModel: (model,transition) ->
#transitionTo 'visits.crud', model
App.VisitsCrudRoute = Em.Route.extend
model: (params,transition) ->
App.Visit.find(params['visit_id'])
If not using UUID's then the routes are different. I did something like this before I moved to UUIDs, it treats model id 'new' as a special case:
App.Router.map () ->
#resource 'visits', ->
#route 'crud', path: ':visit_id'
App.VisitsCrudRoute = App.Route.extend
model: (params, transition) ->
visit_id = params['visit_id']
if visit_id == 'new' then App.Visit.create() else App.Visit.find(visit_id)
serialize: (model, params) ->
return if params.length < 1 or !model
segment = {}
segment[params[0]] = if model.isNew() then 'new' else model.get('id')
segment
For your specific case of managing the wizard step state I would consider using Ember Query Params, which allow you specify the current step in a parameter at the controller level
Query params example:
App.VisitsCrudController = Em.ObjectController.extend
queryParams: ['step'],
step: 'welcome'
Link to next step in the view:
{{#link-to 'visits.crud' (query-params step="directory")}}Next{{/link-to}}
You may also want to define some computed properties for the next and previous steps, and some boolean properties such as isWelcome, isDirectory for your view logic.
I have a nested edit route:
#resource 'dashboard.communities.community', path: ':community_id', ->
#route 'edit'
In my route, I try to retrieve the model with modelFor:
CivicSourcing.DashboardCommunitiesCommunityEditRoute = Ember.Route.extend
model: (params, queryParams, transition) ->
#modelFor('community')
But this returns undefined. The parent route is successfully retrieving the community, though. Any idea what might be going on?
You're resource name is dashboard.communities.community not community
#modelFor('dashboard.communities.community')
Here's a similar example for colors.cool
http://emberjs.jsbin.com/OxIDiVU/442/edit
I have a nested edit route for one of my resources:
#resource 'organization', path: 'organizations/:organization_id', ->
#resource 'organization.edit', path: '/edit'
I link to it like this (using Emblem.js):
linkTo 'organization.edit' organization | Edit
Unfortunately, this results in a url like:
/organizations/4#
Rather than the expected:
/organizations/4/edit
Any idea why this is happening? I experimented with the route syntax a lot. Removing path for organization.edit does nothing, as does a full path: 'organization/:organization_id/edit.
You should be able to get your desired result by using this type of nesting structure:
App.Router.map(function() {
this.resource("organizations", function(){
this.resource("organization", { path: "/:organization_id" }, function(){
this.route("edit");
});
});
});
JSBin example
You're on the right track but #resource is really intended for objects, e.g. organizations. If you're defining an action (not nested resources) you'll want to use #route, i.e.:
#resource 'organization', path: 'organizations/:organization_id', ->
#route 'edit'
I believe that should give you the expected behaviour / routing.
Why not use something like this:
#resource 'organization', ->
#route "edit",
path: "/:organization_id/edit"
In my application I have the following route setup
Orders.Router.map ->
#resource "orders", path: '/', ->
#route 'new'
#route 'show', path: ':order_id'
#resource 'items', path: ':order_id/items', ->
#route 'new'
class Orders.ItemsNewRoute extends Ember.Route
model: (params) ->
Orders.Order.find params.order_id
Within my items.new route, I would like to have a link back to orders.show and am unable to find the best way of going about this.
I cannot find a way to bind my parameter from my URL to the linkTo helper. What would be the best way to go about this?
Ryan,
I'm not 100% sure I understand what your question is but linkTo is very simple to use.
{{#linkTo "orders.show" controller.content}}Show My Order{{/linkTo}}
The above code will send you to the orders.show route with the model being the content of your controller.
Steve
I don't think this is the best way to go about this, but I was able to mess about with the router a bit to make it more like this:
Orders.Router.map ->
#resource "orders", path: '/', ->
#route 'new'
#route 'show', path: ':order_id'
#resource 'items', path: ':order_id/items/new'
class Orders.OrdersRoute extends Ember.Route
model: ->
return Orders.Order.find()
class Orders.OrdersIndexRoute extends Ember.Route
model: ->
return Orders.Order.find()
class Orders.ItemsRoute extends Ember.Route
model: (params)->
return Orders.Item.createRecord
order: Orders.Order.find params.order_id
Then in my template I reference {{#linkTo 'orders.show' order}}
It seems that it was not able to grab a reference from the original :order_id wildcard.
Please see http://jsfiddle.net/kt2Hz/
I have read the docs, api and browsed the source code of Ember. No luck!
The routes:
App.Router.map ->
#resource 'customers', path: 'my_customers', ->
#resource 'customer', path: '/:customer_id', ->
#route 'edit', path: '/my_edit'
App.CustomerEditRoute = Ember.Route.extend
setupController: (controller, model) ->
controller.set('content', model)
alert("inspect: #{Ember.inspect(model)}")
The alert output is "inspect: undefined"
And if I check the params, the object is empty:
App.CustomerEditRoute = Ember.Route.extend
model: (params) ->
alert("inspect: #{Ember.inspect(params)}")
The alert output is "inspect: {}"
the dynamic segment is only passed to the customer route, not the nested ones. so if you change the model hook in your CustomerEditRoute to
model: (params) ->
return this.modelFor("customer")
it should work.
(pretty much the same problem as here btw.)