[Feature] - Add support for a tailwind custom font family config #238
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR introduces a new configuration textarea that allows users to input and validate a JSON configuration for custom Tailwind font families.
The JSON provided by the user overrides the default Tailwind fontFamily settings used in the generated code.
This feature enhances flexibility and enables better brand customization when exporting designs from FigmaToCode.
✨ What's new
Added a textarea config field in the settings panel for Tailwind font customization.
Implemented JSON validation to ensure user input is valid before applying changes.
Added error handling and visual feedback for invalid JSON entries.
📝 Notes
Default Tailwind configuration remains unchanged if the field is empty or invalid.