You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
I’ve searched for any related issues and avoided creating a duplicate issue.
I've searched the community forums to check for related issues or feature requests
Is this feature request relating to an existing component? Please describe.
Component name: control-input react components
Component version: 3.0.1
Both AUradio and AUcheckbox react components have the label prop with a type of PropTypes.string.isRequired. This is fine until I want to have in the label something more than just a plain text, for example one of the words wrapped in a tag like label <b>bold text</b> or maybe I need to add an icon in the label.
The components allow that, so it works, but it will display a warning in the console: "Failed prop type: Invalid prop label of type object supplied to AUradio, expected string."
I think it would be great to change the prop type to PropTypes.node.isRequired
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Request
Is this feature request relating to an existing component? Please describe.
Both
AUradio
andAUcheckbox
react components have thelabel
prop with a type ofPropTypes.string.isRequired
. This is fine until I want to have in the label something more than just a plain text, for example one of the words wrapped in a tag likelabel <b>bold text</b>
or maybe I need to add an icon in the label.The components allow that, so it works, but it will display a warning in the console: "Failed prop type: Invalid prop
label
of typeobject
supplied toAUradio
, expectedstring
."I think it would be great to change the prop type to
PropTypes.node.isRequired
The text was updated successfully, but these errors were encountered: