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
Resolve warnings by allowing fragments to be passed in string props, and more sizes for Decorators
Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
Legacy/CDAI
Legacy/Security
Detailed description
Hi all, we'd like some warnings handled that are being logged in the console with our IBM Products components.
In the ProductiveCard title prop, we are passing a fragment containing an icon and a string instead of just a string so we can match the design given to us.
Similarly with our OptionsTile component, in the summary prop we are passing in an HTML fragment to showcase date, time, etc but it expects a string.
Lastly, in the security Decorator component, there's a console warning when we use it with size 20, we'd like for it to accept sizes other than just 12 and 16.
Our components look and function just fine, but we just want these warnings in the console resolved. Thanks.
The text was updated successfully, but these errors were encountered:
Resolve warnings by allowing fragments to be passed in string props, and more sizes for Decorators
Detailed description
Hi all, we'd like some warnings handled that are being logged in the console with our IBM Products components.
In the ProductiveCard title prop, we are passing a fragment containing an icon and a string instead of just a string so we can match the design given to us.
Similarly with our OptionsTile component, in the summary prop we are passing in an HTML fragment to showcase date, time, etc but it expects a string.
Lastly, in the security Decorator component, there's a console warning when we use it with size 20, we'd like for it to accept sizes other than just 12 and 16.
Our components look and function just fine, but we just want these warnings in the console resolved. Thanks.
The text was updated successfully, but these errors were encountered: