feat(settings): add Enable button for email with logout confirmation#2311
feat(settings): add Enable button for email with logout confirmation#2311evanhutnik merged 2 commits intomainfrom
Conversation
Replace the tooltip/question-mark hint on the disabled email setting with an Enable button that shows an inline confirmation prompting the user to log out and re-authenticate via Google to grant email permissions. Also adds a toast notification when disabling email, and fixes a layout shift in the GitHub row caused by the loading state. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughReplaced the tooltip/popover email-disabled UI with an explicit enable modal and requirements panel, added logout/cancel actions, made the email-disconnect handler async and surface success/failure toasts, and adjusted GitHub "Loading..." fallback markup for consistent layout. Changes
Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@js/app/packages/app/component/settings/Account.tsx`:
- Around line 287-290: The success toast is shown immediately after calling
disconnectEmail() which returns a ResultAsync; change the flow to await/inspect
the ResultAsync returned by disconnectEmail() (or chain its promise) and only
call toast.success('Email disabled …') and setShowEmailModal(false) after a
successful result, while handling errors by showing a toast.error or appropriate
failure handling if the ResultAsync yields an error; locate the call to
disconnectEmail() in the Account component and update it to check the resolved
Result (or use .map/.match/.mapErr) before emitting success UI changes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5744b200-3900-4e78-94b0-fed9f63ffc75
📒 Files selected for processing (1)
js/app/packages/app/component/settings/Account.tsx
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary