#emberjs

is there a way to observe a key stored in a variable?

ie .property(foo, "foo") where foo = "someProperty"

kanja: not sure what that means? i assume you do not mean to observe a property on an object though... property('foo.someProperty')

bbl

Grapho: I do want to property on an object - it's just that which specific property can change so I want to observe the value of a variable

anyone else look at the generated output for HTMLBars, seems to generate a ton of garbage

is it possible to update an {{input}}'s val in a component unit test, and have it trigger bindings?

i have just found https://github.com/dockyard/ember-validations. is it possible (and a good idea) to INJECT it into my models? (instead of using the mixin in each model)

Eskimofo: mixin

Eskimofo: injecting the validations would be assuming it is a standalone service, which it is not

Grapho why, does it have depandencies?

well the mixin taps into the objects init() method to run all its setup

if it were in a service, it could not do that

how can you set a default template to be render in the {{outlet}} of another template?

if it were a service it would need to be designsed to juggle all the validations within itself, rether than letting each object control itso own validationd

For example, if I had an ‘assignments’ template that would render all the assignments in the {{outlet}} by default and other stuff when they click other links?

qwebirc19092: the 'assignments' would actually want to be the index template for that route.. if you want it in the outlet by default.

do i follow a file naming convention to create an index for a template

if im using ember cli?

like assignments.index.hbs?

e.g. assignments.index = app/templates/assignments/index.hbs

ah ok

thank you

your other routes would be like assignments.new... assignments.edit... assignments.whatever

great!

Grapho ok thanks. i will use it as a mixin

Eskimofo: the other benefit of a mixin is it would allow you to validate the same model differently depending on what controller it is on.. but anyway good luck!

is it possible to use `fillIn` helper in a component unit test?

Is the way to create something like a singleton to use an initializer?

I've got a resource that I want to keep track of -- you can only ever have one of this resource at any given time, and I would need access to it in any of my routes. So a route would say "give me the next widget"

Does that sound like an object I create in an initializer and tell it to inject into any route?

samselik_: then doesn't sound like a unit test

highcup: that sounds legit

abuiles: hm. it's a validated-input, so i want to test that, if user enters "123", it works, if they enter "abc", it doesnt

highcup: use dependency injection and a controller that ensures it has a single reference and that the controller is an injected singleton

(and by 'it works' i mean, updates a binding)

is that a component?

{{validated-input value=40}}. render. user enters 'abc' then focuses out. value is still 40.

so yeah, what you said :)

Grapho: and if the object I have in my initializer abstracts network calls to update, does that begin to sound fishy? Or does it still sound right?

{{validated-input value=40}}. render. user enters '80' then focuses out. value is now 80

that sort of thing

highcup: a service could use ajax if it wants

samselik_: I do something like {{validated-input value=attrName object=thing property="attrName"}}

or websocket even

ZiggyTheHamster: if you use a controller for a singleton, do you have to tell it to render on some part of your page for it to work?

then the _controller_ does the validation and makes its results available under thing.errors.attrName

highcup: negative

highcup: actually I think you probably CAN'T have it render if you inject it via initializers, or if you do, it'll be {{render "thing"}} in one place. but it sounds like you don't want that, you just want to be able to get a model and some model-based data

Right

I'm checking out ember services first -- have not used those yet.

Thanks Grapho, ZiggyTheHamster

imho service is better used for accessing and manipulating data that can be used anywhere. controllers, while they could be used a route, are better for displaying data to a template

Grapho: Gotcha. Yeah, the data I want to pass around won't ever be displayed to the user, but will influence my routes. It's almost like a global setting.

So sounds like a service is the way to go.