Skip to content

feat: enhance theme style generator to support Tailwind CSS version 4 #123

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
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: enhance theme style generator to support Tailwind CSS version 4 #123

wants to merge 2 commits into from

Conversation

@aarjun8060
Copy link
Contributor

@aarjun8060 aarjun8060 commented Jun 24, 2025 •
edited by coderabbitai bot
Loading

  • Added tailwindVersion parameter to generateColorVariables and generateThemeVariables functions.
  • Updated sidebar variable handling to differentiate between Tailwind CSS versions.
  • Adjusted theme generation logic to accommodate new parameter for consistent theme styling.

image

image

image

fixes -> #27

Summary by CodeRabbit

  • New Features

    • Theme generation now supports both Tailwind CSS v3 and v4, ensuring correct sidebar color variable naming based on the selected version.

  • Refactor

    • Improved consistency in theme variable naming for different Tailwind CSS versions.

@aarjun8060
feat: enhance theme style generator to support Tailwind CSS version 4
66a56af 
- Added tailwindVersion parameter to generateColorVariables and generateThemeVariables functions.
- Updated sidebar variable handling to differentiate between Tailwind CSS versions.
- Adjusted theme generation logic to accommodate new parameter for consistent theme styling.
@vercel
Copy link

vercel bot commented Jun 24, 2025

@aarjun8060 is attempting to deploy a commit to the tweakcn OSS program Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Jun 24, 2025 •
edited
Loading

Walkthrough

A new utility function changeThemeObjKeyName was added to rename CSS variable keys in theme CSS strings. The generateThemeCode function was updated to use this utility to rename the sidebar CSS variable from --sidebar to --sidebar-background when tailwindVersion is "4". Minor formatting and access style adjustments were also made.

Changes

File(s) Change Summary
utils/theme-style-generator.ts Added changeThemeObjKeyName function; updated generateThemeCode to rename sidebar CSS variable for Tailwind v4; minor formatting and access style changes.

Poem

🐇✨
A key renamed, a theme refined,
From sidebar old to background aligned.
Tailwind’s version now in sight,
CSS variables set just right.
The rabbit hops with code so bright,
Making themes dance in perfect light!
🎨🌿

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

utils/theme-style-generator.ts

Oops! Something went wrong! :(

ESLint: 9.24.0

ESLint couldn't find the plugin "eslint-plugin-react-hooks".

(The package "eslint-plugin-react-hooks" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react-hooks@latest --save-dev

The plugin "eslint-plugin-react-hooks" was referenced from the config file in " » eslint-config-next/core-web-vitals » /node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/eslint-config-next/index.js".

If you still can't figure out the problem, please see https://eslint.org/docs/latest/use/troubleshooting.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66a56af and a2bb4f8.

📒 Files selected for processing (1)
  • utils/theme-style-generator.ts (6 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • utils/theme-style-generator.ts
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@aarjun8060
feat: simplify theme variable handling and add key renaming function
a2bb4f8 
- Removed tailwindVersion parameter from generateColorVariables and generateThemeVariables functions for cleaner implementation.
- Introduced changeThemeObjKeyName function to facilitate renaming of CSS variable keys.
- Updated theme generation logic to utilize the new key renaming function for Tailwind CSS version 4 compatibility.
@jnsahaj
Copy link
Owner

jnsahaj commented Jul 1, 2025

Good change, will have to test it once before I can merge it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aarjun8060 @jnsahaj