-
Notifications
You must be signed in to change notification settings - Fork 4
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
Improved the "Button" UI component #61
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Great job! Button component is refined much better now! |
@kanta1207 |
@kanta1207 I have resolved the conflict. Please review it again. |
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.
Sorry for the late response, didn't reallize there was conflict.
LGTM, great job!
children: React.ReactNode; | ||
} | ||
|
||
const Button: React.FC<IButtonProps> = ({ children, ...props }) => { |
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.
This Button component for Icons looks great, and reusabale to me!
What do you think of the idea of adding this classname to button component, as variant "icon" ?
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.
It's a good idea if this component will be re-used by being called from other files. In this case, however, the Button
component is private, meaning there is no export
keyword on it; thus, I think className
is unnecessary for now. We can add it when it's needed. (YAGNI)
Overview
Improved the
src/components/ui/Button.tsx
file to match it with the Figma design since it was nearly the default state generated by shadcn/ui.Changes
Note