-
Notifications
You must be signed in to change notification settings - Fork 75
Select doesn't work when content is an array of string (dev/master) #57
Comments
I'm using canary. |
As far as I know, that's the expected behavior: the data bound to the select component should be an array of objects, which might then have "name" and "label" attributes that you can use to separate what's displayed in the UI from what's sent to the backend. For example, our documentation pages and demo JS Bin (http://emberjs.jsbin.com/xabeb/1/edit) uses objects that have both names and country codes. I was in the same situation as you recently - just wanted to use a simple array of strings - and I agree it would be great to add this as a feature! If you'd like to make the change and submit it as a PR, that would be great. Otherwise I'd recommend using the workaround of making wrapper objects around your priority values. |
@azirbel this used to work fine on previous versions, the issue for this not working was that I replace the template with something like the following code and it works fine
|
Ok, thanks @abuiles! Didn't realize this used to work. Feel free to make a PR; I'll also take a look when I can, but I'm not sure when I'll get a chance next. |
Actually, my solution partially worked :( I moved to Ember.Select in some Adolfo Builes On Fri, Jul 4, 2014 at 12:53 AM, Alex Zirbel [email protected]
|
@azirbel did you guys fix this? |
I'm afraid not =( it's still on the todo list but there's lots to do. |
When using an array of strings, select doesn't show anything
and
{{select-component content=priority selection=taggingPriority}}
See http://cl.ly/image/2S3o3o2f1o1D
The text was updated successfully, but these errors were encountered: