Fix duplicate font family values in merged configuration #638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Sridhar-C-25 is attempting to deploy a commit to the ct-tailwind-team Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix duplicate font family values in merged configuration
This commit addresses an issue where duplicate font family values were being introduced into the merged configuration when merging with the Tailwind CSS config. Specifically, when the
fontFamilyproperty was set in the Tailwind CSS config with the valuesans: ["Poppins", "monospace"], and then merged using thewithMTfunction, duplicate entries such as["Poppins", "Poppins","monospace","monospace"]were observed.To resolve this issue, I updated the logic in the
withMTfunction to properly merge font family values while avoiding duplicates.