Progress component title prop accepts only a string
See original GitHub issueThe Progress bar accepts only a string. Would it be possible to make it accept a React.ReactNode
instead (or both)?
For example:
Currently passing only text (or string variable):
<Progress title="blah" label={label} />} value={value} />
It would allow a component in place of the title:
<Progress title={<StatusIcon status={StatusType.Warning} label="blah" />} value={value} />
This would be a must have enhancement for the Progress component.
Our product is https://github.com/konveyor/virt-ui
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
the title prop of a button must be a string - react native
Just close the tag after the title attribute ... When I added the 'title' prop, the error was disappeared. That's it.
Read more >Typescript checking error · Issue #1428 · styled-components ...
I solved a similar issue on a input[type=checkbox] extending the Prop interface. In your case define ISVGIconProps like this: interface ...
Read more >React Component Composition Explained | Felix Gerschau
In React, we can make components more generic by accepting props, which are to React components what parameters are to functions.
Read more >React-admin - Field Components - Marmelab
By default, a Field renders an empty string when the record has no value for that field. You can override this behavior by...
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
Enforcing a string will help us solve issues like https://github.com/patternfly/patternfly/issues/3529.
Feel free to reopen if you can’t use a workaround.
@vconzola, thanks. Now I get what’
valueText
is for!