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.
Feature Request: Make multi-select a HOC like Creatable rather than prop on Select?
See original GitHub issueThanks for maintaining react-select!
Currently, there is a problem with simple distinction between single and multi selects. I was wondering a lot why ValueType contains null type rather then just leaving an empty array when I was working on multiselect components. Then, from some issue I’ve understood that it is because of single selects which can be nullable.
But because of this I have to write [...(existingOptions === null ? [] : existingOptions), newOption] in every onChange listener. It causes also weird bugs like #3632.
I think that multi select functionality should be rather implemented as a higher-order component like Creatable rather than part of Select itself.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
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
It looks like it works, but I can not say it sure, because I have ton of problems with types after upgrading. So I will rather wait for rewrite to TS which ensures there are correct type definitions and proper documentation of the type system so that I can be sure the problem is on my side. 🙂
Hi guys, thanks for answering and for your work. I’ll try to upgrade to latest version soon and see what it looks like now. I did not see the code for a while so I can not say right now.