Replies: 2 comments
-
missing required attribute is such a pain... |
Beta Was this translation helpful? Give feedback.
0 replies
-
Better/complete documentation on an action's |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm hoping to compile an FAQ, so I wanted to ask the community what things regarding react-select were/are frustrating from an implementation or understanding standpoint?
I'll start with some of the things I struggled/struggle with in no specific order:
Upgrade guide
Prop documentation/DOM hierarchy
Using the styles api
Hiding input and clearing inputValue onChange/onBlur
value = Object
value
but thevalue.value
Accessing select ref from Async, Createable, and AsyncCreateable
Automated integration testing cannot easily access the menu without certain props being set (perhaps this and animation are a case for hiding the menu instead of render/not render)
Without menu open/close methods, the menuIsOpen prop is a "great power/great responsibility" situation where you're allotted both more control and more complexity as it's not entirely clear in documentation how to handle this especially since many simply want to trigger without being responsible for understanding all of the close-menu conditions (onBlur, onChange, onClear, escape key, etc...). It's also not clear to many that closing it should be done by setting it to undefined and not false.
I'm sure there's more that I am forgetting, but curious what other frustrations others have run into in the interest of lowering the learning curve for everyone.
Beta Was this translation helpful? Give feedback.
All reactions