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
The current tailwind.config.js file has some issues that need to be addressed to ensure proper functionality and maintainability. Specifically, custom utilities are not properly integrated, and there is a misuse of the utilities property.
Problems Identified:
Misuse of utilities Property:
The utilities property is not a valid Tailwind CSS configuration option. Custom utilities should be defined within a plugin using the addUtilities function.
Improper Placement of addUtilities:
The addUtilities function should be used within the plugins array, not directly inside the theme object.
Record
I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue
The text was updated successfully, but these errors were encountered:
Congratulations, @iamabhishek2828! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated, and we look forward to working with you to resolve the issue. Keep up the great work!
We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines
Is there an existing issue for this?
What went down?
The current tailwind.config.js file has some issues that need to be addressed to ensure proper functionality and maintainability. Specifically, custom utilities are not properly integrated, and there is a misuse of the utilities property.
Problems Identified:
Misuse of utilities Property:
The utilities property is not a valid Tailwind CSS configuration option. Custom utilities should be defined within a plugin using the addUtilities function.
Improper Placement of addUtilities:
The addUtilities function should be used within the plugins array, not directly inside the theme object.
Record
The text was updated successfully, but these errors were encountered: