You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with remote query dropdown lists and I've noticed that the custom field key setting for values is not working... It gets completely ignored in fact. I don't know the Semantic UI codebase well enough to issue a pull request and I might break other things but perhaps someone else can fix it?
Example... Setting the field keys.
$('.ui.dropdown').dropdown('setting',{apiSettings: {url: '<api_url>',},fields: {values: 'results',// Custom set result keyname: 'name',value: 'id'}});
In the combined semantic-ui.js file on line 4778. The code currently looks like this.
onSuccess : function(response){module.remove.message();module.setup.menu({values: response.results// This is HARD CODED to results. Should take value from custom defined key});callback();}
Let me know if this needs explaining further or if I'm wrong... I've hacked the code to work for me now.
The text was updated successfully, but these errors were encountered:
bradiosd
changed the title
Query remote for dropdowns using custom values key
[dropdown] Query remote for dropdowns using custom values key
Sep 25, 2015
bradiosd
changed the title
[dropdown] Query remote for dropdowns using custom values key
[Dropdown] Query remote for dropdowns using custom values key
Sep 25, 2015
I'm working with remote query dropdown lists and I've noticed that the custom field key setting for values is not working... It gets completely ignored in fact. I don't know the Semantic UI codebase well enough to issue a pull request and I might break other things but perhaps someone else can fix it?
Example... Setting the field keys.
In the combined semantic-ui.js file on line 4778. The code currently looks like this.
Let me know if this needs explaining further or if I'm wrong... I've hacked the code to work for me now.
The text was updated successfully, but these errors were encountered: