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.

Sign up for GitHub

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

Jump to bottom

Make it possible to opt out of merging behavior with experimentalParseClassName #495

Closed
dcastil opened this issue Dec 3, 2024 · 2 comments · Fixed by #518
Closed

Make it possible to opt out of merging behavior with experimentalParseClassName #495

dcastil opened this issue Dec 3, 2024 · 2 comments · Fixed by #518
Labels
context-v2 Related to tailwind-merge v2 context-v3 Related to tailwind-merge v3 feature Is new feature

Comments

@dcastil
Copy link
Owner

dcastil commented Dec 3, 2024

Request coming from problem stated in #493.
@dcastil dcastil added the feature Is new feature label Dec 3, 2024
@github-actions github-actions bot added the context-v2 Related to tailwind-merge v2 label Dec 3, 2024
@dcastil dcastil mentioned this issue Jan 26, 2025
Merged
@dcastil
Copy link
Owner Author

dcastil commented Jan 26, 2025 •
edited
Loading

This will be addressed in the next major tailwind-merge version. I added the property isExternal to the returned object from experimentalParseClassName that allows to opt out of merging behavior and treat a class like a non-Tailwind class.

I did this as part of the the Tailwind CSS v4 support PR because that behavior is necessary for the new prefix syntax in Tailwind CSS v4.

Done in 380c977.

@dcastil dcastil added the context-v3 Related to tailwind-merge v3 label Jan 26, 2025
@github-actions GitHub Actions
Copy link

This was addressed in release v3.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
context-v2 Related to tailwind-merge v2 context-v3 Related to tailwind-merge v3 feature Is new feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Breaking: Tailwind CSS v4 support dcastil/tailwind-merge
1 participant
@dcastil