#emberjs

ok I'm kinda suck on how I should do routings

stuck*

I'm making a blog and I've got a 'posts' resource

and nested under that I have a 'page' route for pagination

I've got it right now so it's rendering the page route's template above the posts' template

but I guess I'm not sure how to get the page's template to replace posts' instead of displaying both

Inside an observer Ember.observer('value', 'value2', function() {}) is it possible to know which of the watch values triggered the observer?

benlieb: I don't believe so, but it's possible the arguments reveal it?

DoctorDalek: route nesting === template nesting

DoctorDalek: if you don't want nested templates, don't have nested routes

i have some computed prop that observes model and for some reason, it's be triggered twice

on init

anyone know how i can debug this so i can see where its being modified twice?

basically its being fired once with the correct state and a second time with the incorrect state

if i remove this._super.apply(this, arguments); from my setupcontroller, i lose the correct state instance

i haven't been able to track down what's triggering the bad state

buehler?

whoa

im in the container tab in ember inspector

and for some reason i have two instances of a controller

is this normal?

blu____: I usually debounce observers because I've found that there are a lot of instances where we are observing properties in views. These fire twice because the view is initially null and the observer fires then, after it is inserted into the dom, it changes and fires again.

to have two controllers for the route yore in?

The real solution is not to use observers. They're brittle.

yeah ive heard their going the way of the dodo recently

what's a good replacement?

blu____: observers that are not used to affect non-ember state are a code smell IMO

you need to change your mindset. Use a more functional programming paradigm rather than relying on side effects.

blu____: so an observer that observes some data and renders a d3 visualization is fine. An observer that sets other ember properties is not

blu____: there are very few cases where you can't use computed properties to have the data flow that you need

The way I think of it is that you're trying to change your programs state with an observer. Instead, you should explicitly transition through the route.

if I have a nested route like foo/bar/baz, how do I get access to the 'bar' controller from the 'baz' controller?

I tried needs: ['bar'] and var barController = this.get('controllers.bar'); but it died on the 'needs' line

cinnamon_bun: depending on how you set up your routes, you might need `needs: ['foo.bar']`

ember492>#needs must not specify dependencies with periods in their names

uh

maybe it's `foo/bar` then

seems ok. then it has to be 'controllers.foo/bar' in the getter

How would one merge app/components/**/*.css files into app.css with ember cli?

I'm using broccoli-concat to merge all the `app/components/**/*.css` files

thedeeno: https://github.com/ebryn/ember-component-css

It looks like ember-component-css uses mokey patching to get this job done. That seems odd

WebSpirit: hey there, sorry i had to leave the office yesterday. “WebSpirit: so, if I'm looking at employee WebSpirit the flag could be on or off, depending on the time period I've chosen?” correct

so depending on if you have any issues with your shifts in that period, the flag should show next to employee

i think that essentially we need a proxy object