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
Usually, when I'm creating a new component it has 'value=undefined' because my fields are generated in the template. When a user changes from the first option to another one, the update action is triggered and value is set properly. But when user does not trigger 'update' action then 'value=undefined'. I would like to have the first option inside. The patch is quite simple but very likely it should be just the configurable option. What do you think? I'm ready to prepare PR if patch like this is acceptable.
Usually, when I'm creating a new component it has 'value=undefined' because my fields are generated in the template. When a user changes from the first option to another one, the update action is triggered and value is set properly. But when user does not trigger 'update' action then 'value=undefined'. I would like to have the first option inside. The patch is quite simple but very likely it should be just the configurable option. What do you think? I'm ready to prepare PR if patch like this is acceptable.
addon/components/one-way-select.js:didReceiveAttrs()
The text was updated successfully, but these errors were encountered: