-
-
Notifications
You must be signed in to change notification settings - Fork 11
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(CSS): project wide refactoring and cleanup #146
base: main
Are you sure you want to change the base?
Conversation
removing the global CSS in favour of a component
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
interface Props { | ||
children: Snippet; | ||
style?: 'mauve' | 'peach' | 'blue' | 'green' | 'transparent'; | ||
small?: boolean; |
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.
Instead of taking in small
, it'll be better to take in an explicit width
and height
. We could default those to some number if we want.
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.
small
applies to the button size in general, not just the icon size. I don't think we want to use fixed dimensions for buttons?
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.
In that case, we should have an enum called ButtonSize
or equivalent that can either be small
or default
.
This aims to reduce the CSS overhead by removing unused CSS left over from the design stage as well as improving maintanablity by simplifying rule-sets and application.