#emberjs

is it normal for routes to display 2 controllers in the container tab of ember inspector?

s/routes/route

blu____: no

blu____: screenshot?

one sec

@alexspeller http://awesomescreenshot.com/0624xxjq63

blu____: where are you seeing that?

container tab of ember inspector

blu____: looks normal to me

blu____: it's not two controllers

@alexspeller what is it?

blu____: different properties of the controller

alexspeller: oh and its just separated because theyre set at different times?

yes

If I have a model that belongsTo two other models, what's the simplest way to create a new instance of that model and update it with associations?

right now I have a this.store.createRecord to create the new isntance, then I this.store.find() the two associated models, and push the newly created instance to each of them and then call .save()

finally I save the newly created instance

but this doesn't work

alexspeller: is there a proper way to debounce properties set in the controller and the setupcontroller?

or is that an antipattern

blu____: debouncing is very common

Duckily: makes sense

blu____: http://alexspeller.com/debounced-and-throttled-...

Duckily: why not just make it an attribute of your DS.Model?

locks: i’m not sure thats the best conceptually, because ember isn’t aware that the variable is based on a daterange

and you mentioned you normally don't use observers

the variable would be available in other places where employees are used

the other downside is we have reload all of the employee data when payperiod is changed when we really only need to update that variabl

alexspeller: i see what my issue was. thanks for the help, i was looking in the wrong place

alexspeller: your tip to use properties (at least that's what i got out of it) helped

D:

:p

can anyone explain what this._super.apply(this, arguments) does in setupcontroller?

i mean i know what it does, it calls it's super but what is that default behavior?

blu____: ~who knows~

locks: source knows!

Hey guys I saw someone talking about observers/computed properties earlier today. Is the idea that observers should only be used for things that effect the state or saving etc. and CPs are for pretty much anything else.

I dont know if I worded that well

wenincode: observers are for effecting side effects

locks: I think I know what you mean. Is there anything 'bad' about observers

yes, they have a lot of overhead

ya I figured so - thanks friend

np