-
Notifications
You must be signed in to change notification settings - Fork 10.2k
fix: Theme update button staying highlighted when switching back to selected one #22616
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.
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
base: main
Are you sure you want to change the base?
fix: Theme update button staying highlighted when switching back to selected one #22616
Conversation
@kartik-212004 is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
|
WalkthroughThe update modifies the Estimated code review effort1 (~5 minutes) 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
apps/web/modules/settings/my-account/appearance-view.tsxOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-playwright". (The package "eslint-plugin-playwright" 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:
The plugin "eslint-plugin-playwright" was referenced from the config file in ".eslintrc.js". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details:
|
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (07/18/25)1 reviewer was added to this PR based on Keith Williams's automation. "Add community label" took an action on this PR • (07/18/25)1 label was added to this PR based on Keith Williams's automation. |
@kart1ka sir, the PR is ready for review. |
@anikdhabal requires review |
@kartik-212004 I do not see any difference between the before and after video. There also seems to be a type check failing. can you address that as well? |
I think maybe it's not clearly visible in the before and after video, but here's how you can reproduce it - and I will check why the type check are failing |
This PR is being marked as stale due to inactivity. |
What does this PR do?
This PR fixes a form state management issue in the appearance settings where the update button highlight would persist incorrectly when switching back to the original theme selection, particularly when the system theme is selected.
Changes:
Root Cause:
The issue occurred because when "system" theme is selected, it gets stored as
null
in the database but the form expects the string "system". This mismatch caused incorrect dirty state calculations, leading to the update button staying highlighted when it shouldn't.Visual Demo
Video Demo:
Before:
Screencast.from.2025-07-18.12-11-03.mp4
After:
Screencast.from.2025-07-18.12-13-16.mp4
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
Test Steps:
Expected Result:
Test Environment:
Test Data:
Checklist