Bug: search + getOptions bug
See original GitHub issueCodeSandbox Reproduction: https://codesandbox.io/s/react-select-search-bug-29g70?file=/src/App.js
When utilizing search
and a custom getOptions
method, it seems that clicking a result doesn’t set the value, but that keyboard navigating with the Enter
key does set the value.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Need help with bug in Context Search - Mozilla Discourse
getOptions = () => browser.storage.sync.get(null);. I tried replacing the async function with the above and it failed. The context menu would no longer...
Read more >Cannot retrieve parameters of vAxis using getOptions() [62511012 ...
This issue has no mentioned resources. If there were any links or bugs mentioned in the comments or description of the issue, they...
Read more >Problem with filter using getOptions/setOptions - Telerik
Here is my problem. I have a pageable grid with filter and dropdown. It works fine until options are saved and restored from...
Read more >Bug 470207 - IJavaProject#getOptions should return Map<String ...
Markus, this move the Javadoc to the code and should be save. If JDT would accept small improvements, more people would help and...
Read more >Unreal Engine Issues and Bug Tracker (Search Results)
Loading a blueprint that uses the GetOptions meta data causes an ensure ... 3. Fixed. Transform node which transforms a vector from mesh ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@maidul98 react-select depends on the big Emotion library. If you care about performance, it’s not a good choice. Unless your app is already styled with Emotion of course.
Sorry for the delay and thanks @davidangel for the bugfix. I’ve merged it (just tweaked it a bit to work with numeric values) into master. Can be tested here https://react-select-search.com/?path=/story/async--fetch . Published a patch v2.1.1.
@andreymoser Nice! Let me know if you found anything else that is included in your fixes that I’ve missed.