Page MenuHomePhabricator

[lib] Discard keyserver usernames for updateUserAvatarActionTypes
ClosedPublic

Authored by inka on Thu, Jun 20, 7:02 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jun 26, 12:39 PM
Unknown Object (File)
Tue, Jun 25, 8:36 PM
Unknown Object (File)
Tue, Jun 25, 12:12 PM
Unknown Object (File)
Sun, Jun 23, 8:32 PM
Unknown Object (File)
Fri, Jun 21, 1:07 AM
Unknown Object (File)
Fri, Jun 21, 1:07 AM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

inka requested review of this revision.Thu, Jun 20, 7:18 AM
kamil added inline comments.
lib/reducers/user-reducer.js
579–582 ↗(On Diff #41571)

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.Fri, Jun 21, 3:34 AM
lib/reducers/user-reducer.js
579–582 ↗(On Diff #41571)

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.Tue, Jun 25, 1:22 AM
This revision was automatically updated to reflect the committed changes.