-
Notifications
You must be signed in to change notification settings - Fork 24
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
Refactor Accordion [Composition pattern, optimisations, contributing standards] #793
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Ignored Deployments
|
63d7b78
to
7610ea5
Compare
3c72714
to
f320bf0
Compare
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.
Thanks for fixing the type warnings!! It's really good to get these taken care of :) In the future I would suggest creating a separate PR for them for the sake of separating concerns so we can merge changes as soon as their ready
packages/apps/tools/src/components/Common/Layout/partials/Sidebar/Menu.tsx
Outdated
Show resolved
Hide resolved
5b2d04f
to
8ecc832
Compare
Just saying, this is valid too: import React, { type FC } from 'react'; |
There are a lot of changes. A lot of them are just related to making type imports and exports explicit, e.g. instead of:
import React, { FC } from 'react';
we do:
etc.
Not doing this causes warnings in your console. This change doesn't really require review. So, that leaves the primary refactor which is the
Accordion
component. In short, please focus on reviewing:Accordion
in react-uiGeneral PR description
Asana task
This PR primarily aims to refactor Accordion to follow our standards regarding composition structure and other things. Other components like it will be updated in similar fashion in the future so that they all follow the same structure.
Updated Accordion preview
Screen.Recording.2023-08-29.at.10.02.32.mov