Skip to content
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

Merged
merged 20 commits into from
May 15, 2023

Conversation

nikk15
Copy link
Contributor

@nikk15 nikk15 commented May 1, 2023

  • adds Lilypad library
  • replaces existing tooltips and adds tooltips to toolbar buttons
  • condense some larger components and begin swapping to preferred folder structure in the process
Screen.Recording.2023-05-01.at.4.56.20.PM.mov

@nikk15 nikk15 marked this pull request as ready for review May 3, 2023 14:33
@@ -7,8 +7,7 @@
"avatar-page.select": "Seleccionar",
Copy link
Contributor Author

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}
Copy link
Contributor

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> {
Copy link
Contributor

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?

Copy link
Contributor

@nickgrato nickgrato left a 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.

Copy link
Contributor

@nickgrato nickgrato left a 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!

@nikk15 nikk15 temporarily deployed to smoke May 15, 2023 18:35 — with GitHub Actions Inactive
@nikk15 nikk15 temporarily deployed to hc-bio May 15, 2023 18:35 — with GitHub Actions Inactive
@nikk15 nikk15 merged commit c267458 into master May 15, 2023
12 checks passed
@nikk15 nikk15 deleted the add-lilypad-to-dependencies branch May 15, 2023 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants