-
Notifications
You must be signed in to change notification settings - Fork 419
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
Support providing our own Input component #24
Comments
This can be little tricky as this will assume the custom input has onChange, onInput, onKeyDown. |
For Flow types of Typescript users, it is possible to statically enforce that the |
I tried to implement this feature, and assuming than the “wrapper” component will have all the properties and methods of an input element is indeed very tricky with the JavaScript inheritance model. I believe it would be easier to rely on a unique method on the wrapper, like |
I have added this on 1.1.0 alpha |
Are you sure this is already implemented? I can't see any code related to that feature... |
Oh I have not pushed it yet. I am finding input node using document.activeElement (This gives the current focused element). I will push it on the 1.1.0 branch |
Check the 1.1.0-alpha branch. Also added an example of material-ui |
@s-yadav Any news on v1.1 release? edit: I didn't see that the alpha was released on NPM, that's good for me :) |
1.1.0 is released. Thanks. |
Hello,
I would be interested in an additional Prop for the
NumberFormat
component, that would allow the user to provide its ownInput
component implementation. This functional composition pattern would permit, among other thing, the integration of NumberFormat logic with existing input components like http://react-toolbox.com/#/components/input and many othersAny though on that?
The text was updated successfully, but these errors were encountered: