-
Notifications
You must be signed in to change notification settings - Fork 369
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
Replace react-select with something else #305
Comments
Hey Jason I'll be trying this! |
@JasonStoltz Was checking react-responsive-select and it is not able to change its className. Should we change its default styling or change our CSS? |
Aw man, that kinda sucks that they don't pass a custom Just to throw this out there, one other option (if someone else feels really strongly) could be checking out EUI's Select component? 🤷♀ |
So what are our big requirements here? I think they are that:
I'd be fine with considering the EUI Select as long as it's possible to use it without requiring all of EUI as a dependency. |
I agree with the accessibility requirement, but why we don't want the select to use inline styles?
@JasonStoltz What's the issue? |
Hey @Jfelix61, I see that you created a PR replacing react-select with react-responsive-select. I think changing the underlying UI library is a big change for Search UI, what was your reasoning behind choosing react-responsive-select among other libraries? I want to be sure that we're making the right decision here. |
I think react-responsive-select in the first message was just an example, and we should research other libraries as well. |
Hi @yakhinvadim, I researched other libraries with a screen reader enabled and the one that had the best accessibility was react-select (EUI has good accessibility too, but I can't find if it currently has tree shaking). |
Wow, that's great news! But my thinking is that since react-select has the best accessibility out there and strict CSP issue is going to fix itself after we upgrade dependencies, it's probably not worth it to replace the library. I expect that if we replace it, we'd face other issues that are already solved by react-select. Eager to hear your thoughts. |
That's great to know, I love react-select so I have no problems in keeping it. Then, if it's breaking, it would be better to upgrade for the v2.0 breaking version right? |
Yes, I think so. |
I believe search-ui has depended on react ^16.8 for quite a while now. Does that mean it is possible to upgrade to the latest version of react-select? Personally I have no problem with react-select and it looks like the plans to replace it are not moving forward. Meanwhile, react-select has introduced some accessibility improvements I would love to use. |
We updated react-select recently, and it sounds like it's a lot more pleasant to work with: #776. I'm going to close this issue. |
Additionally, the inline styles cause an issue with CSR.
Relates to #93
The text was updated successfully, but these errors were encountered: