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

chore: improve styling process with tailwind-merge #148

Closed
jaipaljadeja opened this issue Apr 12, 2024 · 0 comments · Fixed by #149
Closed

chore: improve styling process with tailwind-merge #148

jaipaljadeja opened this issue Apr 12, 2024 · 0 comments · Fixed by #149
Assignees

Comments

@jaipaljadeja
Copy link
Contributor

Add tailwind-merge library and combine it with existing classnames library by making a custom util function to have more control and optimizations of tailwind classes in various scenarios.

Example Scenario:

lets take the Button UI component for instance, when we pass more classes (ex- 'px-2') via props, css still gives specificity to 'px-4' of the Button component itself, to solve this we sometimes use ! (important selector) but that's not a good common practice to use it every time. so tailwind-merge will help here.. it will only output the class added last in the order, also remove redundant classes and possibly try to merge classes as well.

I can do this, would you mind assigning it to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants