{"action":"created","issue":{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/3293","labels_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/3293/labels{/name}","comments_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/3293/comments","events_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/3293/events","html_url":"https://github.com/Semantic-Org/Semantic-UI/issues/3293","id":115422434,"number":3293,"title":"Unable to store complex data for each item of a dropdown","user":{"login":"nathanpalmer","id":125599,"avatar_url":"https://avatars.githubusercontent.com/u/125599?v=3","gravatar_id":"","url":"https://api.github.com/users/nathanpalmer","html_url":"https://github.com/nathanpalmer","followers_url":"https://api.github.com/users/nathanpalmer/followers","following_url":"https://api.github.com/users/nathanpalmer/following{/other_user}","gists_url":"https://api.github.com/users/nathanpalmer/gists{/gist_id}","starred_url":"https://api.github.com/users/nathanpalmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nathanpalmer/subscriptions","organizations_url":"https://api.github.com/users/nathanpalmer/orgs","repos_url":"https://api.github.com/users/nathanpalmer/repos","events_url":"https://api.github.com/users/nathanpalmer/events{/privacy}","received_events_url":"https://api.github.com/users/nathanpalmer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/labels/Evaluating%20Bug%20/%20Change","name":"Evaluating Bug / Change","color":"f7c6c7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-06T02:41:45Z","updated_at":"2015-11-11T01:28:58Z","closed_at":null,"body":"Something we support on the Semantic-UI-Ember side is storing a model for each item of the dropdown and setting that model when it's selected. This works great for when you're setting up a relationship within Ember-Data.\r\n\r\nHowever, it seems this change casts anything within data to a String and breaks this functionality completely.\r\n\r\nhttps://github.com/Semantic-Org/Semantic-UI/commit/c43ea73f7f0622441dc13cbee067ecbb1114c5b9#diff-dbb1b936fdad1f63b3a01f86d9a54fd1L1565\r\n\r\nFor now we've downgraded to version 2.0.8 which is right before that part was released.\r\n\r\nHere is an example of how we're using it: https://github.com/Semantic-Org/Semantic-UI-Ember/blob/ce7cff9b40a2d83f1231dd081f3dec878b195d93/tests/dummy/app/templates/modules/dropdown.hbs#L52"},"comment":{"url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/comments/155625414","html_url":"https://github.com/Semantic-Org/Semantic-UI/issues/3293#issuecomment-155625414","issue_url":"https://api.github.com/repos/Semantic-Org/Semantic-UI/issues/3293","id":155625414,"user":{"login":"nathanpalmer","id":125599,"avatar_url":"https://avatars.githubusercontent.com/u/125599?v=3","gravatar_id":"","url":"https://api.github.com/users/nathanpalmer","html_url":"https://github.com/nathanpalmer","followers_url":"https://api.github.com/users/nathanpalmer/followers","following_url":"https://api.github.com/users/nathanpalmer/following{/other_user}","gists_url":"https://api.github.com/users/nathanpalmer/gists{/gist_id}","starred_url":"https://api.github.com/users/nathanpalmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nathanpalmer/subscriptions","organizations_url":"https://api.github.com/users/nathanpalmer/orgs","repos_url":"https://api.github.com/users/nathanpalmer/repos","events_url":"https://api.github.com/users/nathanpalmer/events{/privacy}","received_events_url":"https://api.github.com/users/nathanpalmer/received_events","type":"User","site_admin":false},"created_at":"2015-11-11T01:28:58Z","updated_at":"2015-11-11T01:28:58Z","body":"It makes sense when you're trying to match up with values that were defined in HTML only.\r\n\r\nHowever, in our rich javascript world everything is wrapped in a component and upon initialization it is setting the value to what it should be. Having to work with strings will add some unnecessary complexity to any dropdowns that we have because on each value change we'll need to search the data store for the right corresponding record and then emit it from the component. Where-as now each record is bound to the item itself so we simply take that and return it.\r\n\r\nFrom Semantic-UI-Ember we're trying to keep it a lightweight library on top of Semantic-UI since I find it unnecessary to re-implement the Javascript parts that have already been developed.\r\n\r\n"}}