Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Carbon: numeric text field should use its own component
See original GitHub issueThe text-field component with a numberic input should use the NumberInput carbon component instead of the TextInput one.
https://www.carbondesignsystem.com/components/number-input/usage
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Text input – Carbon Design System
Text inputs enable users to enter free-form text data. The type of text field used should reflect the length of the content you...
Read more >Phone number field with country selector (new component ...
New component. I design the IBM Registration forms on the URX squad and there is no phone number field with a country code...
Read more >React Text Field component - Material UI
Text Fields let users enter and edit text. Text fields allow users to enter text into a UI. They typically appear in forms...
Read more >Number input
Number inputs are similar to text inputs, but contain controls used to increase or decrease an incremental value.
Read more >Text fields - Human Interface Guidelines
A text field can contain placeholder text — such as "Email" or "Password" — when there's no other text in the field. Because...
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
I was told that if there’s a numeric input, we should use this one instead of the regular one…so that’s what I did in the PR
🎉 This issue has been resolved in version 2.20.0 🎉
The release is available on
react-form-renderer (@latest dist-tag)
pf3-component-mapper (@latest dist-tag)
pf4-component-mapper (@latest dist-tag)
mui-component-mapper (@latest dist-tag)
Demo can be found here!