-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow value to be changed from higher level #108
Comments
I had a similar scenario where I would render typehead with different value when user clicked on something, so I've made the following modification that seems to work for me: |
@yurynix did you make a pull request? I need this feature too. For instance to empty the input when the user clicks on an x symbol at it's right side |
@yurynix Your proposed change would be very useful for me too. I wish I could provide feedback but I'm not familiar enough with the module either. |
#133 Seems to solve a niche problem. If |
@smith-kyle As you can see from the commit, the code change is very minor. |
@yurynix I've been testing you change, which works great in our setup, but I made two minor changes. First I allowed to clear the typeahead by passing a falsy value to |
@danieljuhl Sounds great, can you provide a link for your changes? |
@yurynix https://github.com/kodyl/react-typeahead/tree/react-0.14, but please notice that I also made changes to avoid errors and warnings when used with |
@danieljuhl Thanks! |
It seems that
value
is only used on component construction, and not respected if changed afterwards.I would like to be able to change the value / default value of the component based on an external value.
The text was updated successfully, but these errors were encountered: