-
Notifications
You must be signed in to change notification settings - Fork 842
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
Formalize useColorPicker
as a component export
#2895
Comments
@thompsongl I want to work on this. Is it related to the src/docs part |
@Dilshaad21 This change is stand-alone and wouldn't interact with other changes or parts of EUI; specifically it's moving I'd recommend renaming this helper to something like |
Ok @chandlerprall, going for it |
|
@Dilshaad21 Are you working on this? |
@thompsongl Can I work on this issue? |
I've made some modifications to the function in #2850. We should wait until that PR merges before moving forward again with work on this issue |
#2850 has been merged, this is ready to be worked on @mridulgogia |
Done in #3067 |
Looks like
useColorPicker
is probably a service we'll want to document and export if it's this helpful in a consuming application?Originally posted by @cchaos in #2850
This idea extends beyond this case to other components with slightly-non-standard form element input-output expectations.
The text was updated successfully, but these errors were encountered: