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 May 17, 2023. It is now read-only.
Instead, we should expand this to also allow a React component to be passed. For example:
constMyComponent=props=>{constdescription=<Paragraph>Here is some <strong>rich-formatted</strong> helper text.</Paragraph>;return(<Form><Form.TextInputlabel="Form label"description={description}/></Form>);};
If the description value is a string, it should just be rendered as plain text.
The text was updated successfully, but these errors were encountered:
Right now, if the user supplies a string, we're doing replacement of backticks with <Code> components, similar to Markdown. Do we want to keep this behavior?
On one hand it might be nice to provide a simple shortcut, but I worry that having two alternatives might be a bit confusing.
On Form Fields, the
description
prop (which shows the "helper text" beneath the field) must be a string. For example:Instead, we should expand this to also allow a React component to be passed. For example:
If the
description
value is a string, it should just be rendered as plain text.The text was updated successfully, but these errors were encountered: