#emberjs

tinobauer: why do you want to do that

locks: because of a locale change.

observers don't work, because i'm changing the locale for another library, too, which i cannot observe

hhmm

also, i use it all over the place, so i don't want to start messing around with observers

triggering a page reload doesn't work?

tinobauer -- there's #reset on the application, but thatll clear out your models and store too

not sure that works

tinobauer: try document.location.reload()

SaladFork: locks: these are two things i wanted to avoid.

i want to keep all state, just force a rerender

i tried this.container.lookup('view:toplevel').rerender();

but that didn't do anything

What’s the canonical way to use query params in a model hook right now? I thought they’d show up on the params argument, but it seems like they don't...

tinobauer: Not sure if this would work for you, but check out this SO post: http://stackoverflow.com/questions/14290316/obs...

something is confusing me, if you're manipulating the models it should update

so there's no canonical way to rerender, right?

and like, cascade the changes through the observers

only rerender

which you shouldn't have to call yourself typically, because of the data bindings

locks: as i said, the data bindings don't make sense.

i don't want to have all my date attributes to observe the locale, that just doesn't make sense

ForSpareParts: I don't know about canonical, but I had the same issue in my app. What I ended up doing was just doing `this.set('myQP', val)` in the beforeModel hook, since you can get at the QPs from the transition object

ForSpareParts: did you specify in the route which query params you want?

locks: you can do that? I thougth QPs were a controller thing

locks: yep. and in the controller, too.

GreenCoal: you're supposed to, see the guides

ForSpareParts -- you should get queryParams on the params object in the model hook if you declare the queryparams on the route too

locks: the guides tell you to specify them on the Controller

they only mention specifying on routes when they talk about configuring refresh behavior later and stuff

hm, OK. Maybe my query parameters are getting populated, and I’m just not setting the values right when I transition. derp.

Any thoughts on an idiomatic way to represent a singleton model?

If I have a set of Images

and one of them is the background.

I doesn't feel right to create a new model for it

BackgroundImageService

thanks locks

If a Parent hasMany Children, and a Child hasMany Grandchildren, how can I have a computed property that returns all of the Parent's Grandchildren through its Children?

something like children.reduce(function (reduced, child) { reduced.pushObject(child.get('grandChildren')); }), []) ?

KerrickLong: Is this with ember-data, or plain old ember objects?

GreenCoal: Ember data.

Are the relationships async?

Not explicitly marked as async: true or async: false -- whatever the default is.

But they _are_ using DS.EmbeddedRecordsMixin.

are there any clever ways of produce the same output as {{render context model}} where context is a variable and not a string?

producing*

dadamssg: could you use a named outlet?

GreenCoal: ahh yes, forgot about that. thanks!

but {{render context model}} is exactly how you'd do it

KerrickLong: I ask because I wouldn't want the CP to fire off ajax requests for additional records if they weren't already loaded - CPs shouldn't cause side effects. I think relationships are synchronous by default currently, so I'd think that locks' suggestion should get you about there

Do nested routes (not resources) also have nested templates?

mellatone: each level has it's own template

The problem with locks' solution is that the dependent keys don't support nested @each. I'd have to make it dependent upon parent.children.@each.grandchildren.@each.

mellatone: the only difference between routes and resources is that routes do not reset the namespace

mellatone: and you should use routes going forward

you don't need a nested each

and that dependent key looks wrong

nvm

parent.children.@each.grandchildren.[] should work no?

locks: are resources being deprecated at some point?

unless there’s an instance where you want it namespaced right?

mellatone: that's how I use them

like PeopleAdd vs EmailAdd, same route “name” but entirely different purposes

GreenCoal: yes

you misunderstand

you'd only have such a problem with resources because they reset namespace

so this.resource('add') is top level regardless

if you have this.route('people') { this.route('add') }

then the full name is PeopleAdd

hi

ah, I see

in my controller, how do I do something for each item in my model?

I have an async relation where I'm doing myModel.get('asyncRelation').mapBy('title') but I'm getting undefined as the result of the map

is there a way to have the map be triggered only when the asyncRelation loads?

Weezey: maybe a computed property that evaluates the array and returns an array?

locks: That worked, thanks!