Page MenuHomePhabricator

[lib] Discard keyserver usernames for updateUserAvatarActionTypes
ClosedPublic

Authored by inka on Jun 20 2024, 7:02 AM.
Tags
None
Referenced Files
F3497781: D12514.diff
Thu, Dec 19, 7:59 PM
Unknown Object (File)
Sun, Dec 15, 3:05 AM
Unknown Object (File)
Sun, Dec 15, 3:05 AM
Unknown Object (File)
Sun, Dec 15, 3:05 AM
Unknown Object (File)
Sun, Dec 15, 3:04 AM
Unknown Object (File)
Sun, Dec 15, 3:04 AM
Unknown Object (File)
Sat, Dec 14, 5:44 PM
Unknown Object (File)
Tue, Dec 10, 7:48 PM
Subscribers

Details

Summary

issue: ENG-8365

Test Plan

Tested that for updateUserAvatarActionTypes if the user was in the store the username is not changed. Assuming some correctness based on having tested other diffs in this stack

Diff Detail

Repository
rCOMM Comm
Branch
inka/userStore
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

inka requested review of this revision.Jun 20 2024, 7:18 AM
kamil added inline comments.
lib/reducers/user-reducer.js
579–582

A bit confusing because this code is doing basically nothing - but it's probably good to leave it to keep it consistent with other call sites

This revision is now accepted and ready to land.Jun 21 2024, 3:34 AM
lib/reducers/user-reducer.js
579–582

Looking at the code called by updateUserAvatarResponder - updateUserAvatar -> createUserAvatarUpdates -> createUpdates is actually seems like we can get updates for some other users here. So this code could do something. And it doesn't hurt

This revision was landed with ongoing or failed builds.Jun 25 2024, 1:22 AM
This revision was automatically updated to reflect the committed changes.