-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add Lilypad Tooltip component to existing tool bar buttons #6058
Conversation
@@ -7,8 +7,7 @@ | |||
"avatar-page.select": "Seleccionar", |
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.
You can ignore the language files. These are just formatting updates from my attempt to add translations, which have been removed
@@ -50,6 +51,7 @@ export const ToolbarButton = forwardRef( | |||
)} | |||
disabled={disabled} | |||
title={title} | |||
onClick={onClick} |
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 in this PR but as the FE matures it might be good to remove these {...rest} catch alls, side note I know they where there, I just think they can be cleaver yet misleading, you are establishing these nice prototypes soon to be TS type and I think it would be nice to have concrete props being sent to the component with no wild card catch all.
defaultMessage: "Open the chat sidebar (T)" | ||
}); | ||
|
||
interface ChatToolbarButtonProps extends RefAttributes<any> { |
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.
We usually opt in to using types before interfaces. type ChatToolbarButtonPropsT = {}
This other suggestion is stylistic, we do it in the subscription team but we end interface,type, and enum with the first initial of what it is. CategoriesE, ButtonsI ,ChatToolbarButtonPropsT etc.
I don't think extends RefAttributes is being used here?
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.
for the most part the pr looks good bu the chat context has quite a few "any"s, ideally noting is an any unless we have no other choice or it's intentional.
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 blocking changes, can clean up a few things but i think you got it!
Screen.Recording.2023-05-01.at.4.56.20.PM.mov