Skip to content
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

HexColorInput #157

Open
dcworldwide opened this issue Sep 18, 2021 · 4 comments
Open

HexColorInput #157

dcworldwide opened this issue Sep 18, 2021 · 4 comments

Comments

@dcworldwide
Copy link

dcworldwide commented Sep 18, 2021

For those that use UI frameworks (i.e. MUI), it would be nice if the HexColorInput could allow the rendering to be outsource to the UI framework input, with the logic of HexColorInput being a hook/decorator.

Or alternatively, I am ok to build my own input component by using the HexColorInput component as a guide, but to to do that it would be great if that component's interfaces were accessible publicly.

i.e.

import { ColorInputBaseProps } from "../types";
import { validHex } from "../utils/validate";
import { ColorInput } from "./common/ColorInput";
@omgovich
Copy link
Owner

omgovich commented Sep 20, 2021

Hi! That's actually a great idea and I definitely should implement something like const props = useHexColorInput() 👍

@CharcoalStyles
Copy link

Running into this problem, too 😄

@MarufSharifi
Copy link

i have the same problem

@Bartel-C8
Copy link

Bartel-C8 commented Sep 5, 2022

Related request here, I would like to overrule e.g. the validate from HexColorInput (to only allow #rrggbb).
But as the {...rest} is spread in the beginning, I cannot hack this around (as it is not defined in the TS interface).

Would be nice to export the ColorInput to make my own HexColorInput.
Or give more options to HexColorInput.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants