Support providing our own Input component
See original GitHub issueHello,
I would be interested in an additional Prop for the NumberFormat
component, that would allow the user to provide its own Input
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 others
import MaterialDesignInput from 'react-toolbox/lib/input';
<NumberFormat inputComponent={MaterialDesignInput} />
Any though on that?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Support providing our own Input component #349 - GitHub
Hello, I would be interested in an additional Prop for the MaskedInput component, that would allow the user to provide its own Input...
Read more >How to make a Custom Input Component | Sanity.io guide
Step-by-step guide to create a custom input component.
Read more >Building Custom Input Components for Blazor using InputBase
In this post, I'm going to show you how you can create your own input components using InputBase as a starting point.
Read more >Creating Custom Form Input Components with ... - Elite Ionic
In this tutorial, we explore how to add a ControlValueAccessor to a custom input component to allow it to interact with the Angular...
Read more >Input types for custom components - Builder.io
When you create custom components to use in Builder, there are two required inputs and a number of optional inputs to help you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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
1.1.0 is released. Thanks.