Details
Able to remove an avatar and the behavior is to be expected with removing an avatar and the loading state returns the correct values when the set avatar request was happening
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
native/avatars/edit-user-avatar-provider.react.js | ||
---|---|---|
45–48 ↗ | (On Diff #25715) | This may seem unnecessary but the very next diff will add another condition that will make this block necessary |
native/avatars/edit-user-avatar.react.js | ||
46–49 ↗ | (On Diff #25715) | Eventually we will be able to get rid of this when all the loading logic is put into the edit user avatar provider (a future diff) |
native/avatars/edit-user-avatar-provider.react.js | ||
---|---|---|
45–48 ↗ | (On Diff #25715) | Edit: not the very next diff but the diff after the next diff |
Small fixes
native/avatars/edit-user-avatar-provider.react.js | ||
---|---|---|
45–48 ↗ | (On Diff #25715) | There's no point memoizing a boolean, especially when it's such a simple calculation (even in D7621). Your intuition for memoization is off... ask me about this in the office tomorrow. (Please remove the React.useMemo) |
61 ↗ | (On Diff #25715) | We should still throw here so we emit an UPDATE_USER_AVATAR_FAILED instead of UPDATE_USER_AVATAR_SUCCESS |