fix(desktop): preserve existing terminal presets during initialization#1421
Conversation
initializeDefaultPresets() was overwriting user presets when terminalPresetsInitialized was null. Now checks for existing presets first and only applies defaults when none exist.
📝 WalkthroughWalkthroughModified Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 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. Comment |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
Summary
initializeDefaultPresets()was overwriting existing user terminal presets whenterminalPresetsInitializedwas nullChanges
apps/desktop/src/lib/trpc/routers/settings/index.ts: ChangedinitializeDefaultPresets()to check for existingrow.terminalPresetsbefore applying defaults. If presets already exist, they are kept as-is and only theterminalPresetsInitializedflag is set totrue.Test Plan
terminalPresetsInitializedis nullterminalPresetsInitializedis already trueSummary by CodeRabbit