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 conflictingClassGroupModifiers in config non-optional #216

Closed
dcastil opened this issue Apr 2, 2023 · 1 comment · Fixed by #291
Closed

Make conflictingClassGroupModifiers in config non-optional #216

dcastil opened this issue Apr 2, 2023 · 1 comment · Fixed by #291
Labels
breaking Is breaking change context-v2 Related to tailwind-merge v2 feature request
Milestone
v2

Comments

@dcastil
Copy link
Owner

dcastil commented Apr 2, 2023

Had to make it optional in #214 not to introduce a breaking change. But optional keys in config make plugins check every config object for existence before it can be used since config objects can be undefined.
@dcastil dcastil added breaking Is breaking change feature request labels Apr 2, 2023
@dcastil dcastil added this to the v2 milestone Apr 2, 2023
@dcastil dcastil mentioned this issue Aug 19, 2023
Merged
@github-actions
Copy link

This was addressed in release v2.0.0.

@dcastil dcastil added the context-v2 Related to tailwind-merge v2 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
breaking Is breaking change context-v2 Related to tailwind-merge v2 feature request
Projects
None yet
Milestone
v2
Development

Successfully merging a pull request may close this issue.

Make conflictingClassGroupModifiers in config non-optional dcastil/tailwind-merge
1 participant
@dcastil