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

Adding tailwind-merge to improve styles customization #671

Open
soykje opened this issue Apr 25, 2023 · 0 comments
Open

Adding tailwind-merge to improve styles customization #671

soykje opened this issue Apr 25, 2023 · 0 comments

Comments

@soykje
Copy link
Contributor

soykje commented Apr 25, 2023

Description

Actually if we want to override a specific property (let's say height) from one of our components, we can pass specific tw classes. But in the end we'll get two properties, and according to natural priority rules, our customization won't work.

Problem Statement/Justification

ex: I have a component with a h-sz-24, but on a specific implementation I want to set h-auto. This last rule will be written to DOM but not used, as first one will have priority.

The tailwind-merge package should fix this problem, instead of using a ! modifier. But as we're having a custom Tailwind config, we should also adapt the taiwind-merge one.

Proposed Solution or API

tailwind-merge

Alternatives

No response

Additional Information

No response

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

No branches or pull requests

1 participant