-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input styling changes, Form component addition #216
Conversation
@@ -80,14 +87,14 @@ export function Tooltip({ | |||
}) { | |||
return ( | |||
<TooltipWrapper hasChrome={hasChrome} data-placement={placement} ref={tooltipRef} {...props}> | |||
{hasChrome && <Arrow data-placement={placement} ref={arrowRef} {...arrowProps} />} | |||
<Arrow isVisible={hasChrome} data-placement={placement} ref={arrowRef} {...arrowProps} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding this one!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No prob -- did you run into this issue as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea, while adding the search dropdown on the blog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about that one typing but, other LGTM
@ghengeveld I reworked this w/ the pattern we discussed on the call today. I think it ends up being more flexible, as you say. LMK what you think. |
👏 |
🚀 PR was released in |
The
Input
element has new styling, per the designs here:https://projects.invisionapp.com/d/main#/console/20597416/432876968/preview
In addition to that, I have added a "lightweight"
Form
component that does not make any assumptions about how you manage form state (values, onChange, etc.), though it does encode some UX patterns for how we handle error messages & validate form fields. The intent was to make this extremely flexible, but create a set of behaviors that we will want on form across our properties based on the design language. I added some example for how to manage state in the stories, but they are mostly meant for documentation/example purposes.The API is backwards compatible, so I am setting this to a
minor
release.PS this will be the first design system component I added w/ TypeScript so let me know what I can do to improve that 👍