You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 seth-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 thetaiwind-merge
one.Proposed Solution or API
tailwind-merge
Alternatives
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: