fix(web): sync avatar changes immediately after profile update

[wally-an]

Summary

Fixes #5878 - Profile picture changes are not reflected in the UI after the initial change. Users must reload the page to see updated avatars.

Root Cause

The v0.28.0 "redesign account and SSO management" migrated from MobX to React Context + React Query. The migration broke the reactivity chain because AuthContext.currentUser was never updated after the initial initialize() - only React Query cache was updated. Components reading from useCurrentUser() continued showing stale avatar data.

Changes

After a successful profile update, AuthContext.currentUser is now synced with the updated user data, triggering immediate UI updates across all components consuming useCurrentUser().

• Added setCurrentUser function to AuthContext that updates both the context state and React Query cache
• UpdateAccountDialog calls setCurrentUser(updatedUser) after successful profile save

Validation

• pnpm test — all tests pass
• Manual testing: avatar updates immediately in user menu and settings header after save

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 26583abc-555d-47bf-8625-7a4be8e57ff6

📥 Commits

Reviewing files that changed from the base of the PR and between 3b930e4 and 71af95e.

📒 Files selected for processing (2)

• web/src/components/UpdateAccountDialog.tsx
• web/src/contexts/AuthContext.tsx

🚧 Files skipped from review as they are similar to previous changes (2)

• web/src/components/UpdateAccountDialog.tsx
• web/src/contexts/AuthContext.tsx

---

📝 Walkthrough

Walkthrough

Adds a new setCurrentUser API to the auth context to update current-user state and React Query cache; UpdateAccountDialog now captures the result of updateUser and calls setCurrentUser(updatedUser) immediately after a successful update, before showing success feedback and closing.

Changes

Cohort / File(s)	Summary
Auth context update web/src/contexts/AuthContext.tsx	Adds setCurrentUser: (user: User | undefined) => void to the context value and implementation. Updates state.currentUser and synchronizes React Query cache for the current-user and user-detail queries, including removal when undefined.
Account update flow web/src/components/UpdateAccountDialog.tsx	Imports useAuth, captures the resolved updateUser result as updatedUser, and invokes setCurrentUser(updatedUser) immediately after update succeeds and before toast.success, onSuccess, and closing the dialog.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main fix: syncing avatar changes immediately after profile update, which directly addresses the core issue.
Description check	✅ Passed	The description is clearly related to the changeset, explaining the root cause, solution, and validation for the avatar sync issue.
Linked Issues check	✅ Passed	The PR successfully addresses issue #5878 by syncing AuthContext.currentUser and React Query cache after profile updates, ensuring avatars update immediately without requiring a page reload.
Out of Scope Changes check	✅ Passed	All changes (adding setCurrentUser to AuthContext and calling it in UpdateAccountDialog) are directly scoped to fixing the avatar sync issue described in #5878.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

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 `@web/src/contexts/AuthContext.tsx`:
- Around line 159-165: The setCurrentUser callback updates context state but
does not clear React Query's cached user data when passed undefined; update
setCurrentUser so that when user is undefined it also synchronizes the cache by
clearing or resetting the relevant queries (e.g., call
queryClient.setQueryData(userKeys.currentUser(), undefined) and remove or set to
undefined the userKeys.detail(...) entry or use queryClient.removeQueries for
those keys) while keeping the existing behavior when user is present; locate the
logic in the setCurrentUser function and update the branch that handles user
falsy values to mirror the cache update performed in the user-present branch.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 49981afd-a4e7-4046-b2d1-5ad18549e17f

📥 Commits

Reviewing files that changed from the base of the PR and between 616487f and 3b930e4.

📒 Files selected for processing (2)

• web/src/components/UpdateAccountDialog.tsx
• web/src/contexts/AuthContext.tsx

[boojack]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".