Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SelectSearch ignores not changed value after async onChange
See original GitHub issueHi!
It seems that SelectSearch ignores not updated value prop after async onChange.
Let say the value is ‘1’, onChange calls API and (after validation or whatever reason) value didn’t actually update then SelectSearch still shows previously clicked option as a selected one. Which is wrong. So it looks like the internal state is not updated and it mismatches with the provided value from now on.
My workaround is to use a key prop but it’s masking the actual problem in the end. 🤷🏻
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry for the late reply @Ronny25 . Yes, seems like something has broken with the controllable state. I’ll take a look
@icaroscherma
onSelectwill be triggered only whenvaluehas changed - it means when it’s a primitive string it won’t detect change (when it has previous value). So I would maybe stick to usingkeyprop. Seems a bit cleaner as for me instead of using additional state or monkeypatching. Thanks.