Referencing property names about ember-cli-selectize HOT 4 CLOSED

@ksnyde my bad.
While converting from a previous non-jshint-passing to a cool-jshint-passing project, i missed some brackets in the option creation. Sorry.
v0.0.5 should fix your issues like #2.

I also included a very very simple dummy test app. This app should become the next demo later.

Option paths are expected to start with content., just like Ember.Select expects. Originally this project goal was to completely replace Ember.Select, and it still is compatible!

Thanks and sorry again. Please report any problems.

You can also refer to the old project issues which may contain useful info: https://github.com/miguelcobain/ember-selectize/issues

from ember-cli-selectize.

This problem still exists. I have tried various combinations including:

• id - results in "undefined"
• content.id- results in "undefined"
• content.content.id - results in "undefined"
• content.content.content.id - results in NO OPTIONS

for the situation I outlined above, what would you expect to work?

from ember-cli-selectize.

Ok, i'm an idiot. I was referring to content.name and the model's mock is out of date and doesn't HAVE that property. Arrgh. Problem sorted.

would be nice if there were an error in this situation but beggars can't be choosers. I may get a PR to you with this if I can catchup on lost time from my general silliness of earlier today.

from ember-cli-selectize.

It happens. :)

Just for reference, that string you use is simply getting passed to a get call to each item in content.

from ember-cli-selectize.