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

Expect all prefixes to be valid Tailwind prefixes #39

Closed
dcastil opened this issue Oct 21, 2021 · 1 comment · Fixed by #50
Closed

Expect all prefixes to be valid Tailwind prefixes #39

dcastil opened this issue Oct 21, 2021 · 1 comment · Fixed by #50
Labels
context-v0 Related to tailwind-merge v0 feature request

Comments

@dcastil
Copy link
Owner

dcastil commented Oct 21, 2021

I think there is no reason to restrict the available prefixes. Removing the hardcoded ones in the default config could reduce bundle size, reduce the need to use a custom tailwind-merge config and speed up the library a little bit.
@dcastil
Copy link
Owner Author

dcastil commented Oct 21, 2021

Could lead to issues if people use : in their non-Tailwind classes. But in that case, I could add an optional checkPrefixes callback to the config which could be provided by the library user.

@dcastil dcastil changed the title Allow all prefixes programmatically Expect all prefixes to be valid Tailwind prefixes Oct 21, 2021
@dcastil dcastil mentioned this issue Oct 21, 2021
Merged
@dcastil dcastil added the context-v0 Related to tailwind-merge v0 label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
context-v0 Related to tailwind-merge v0 feature request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Consider all prefixes as valid Tailwind prefixes dcastil/tailwind-merge
1 participant
@dcastil