Change Details

In the past the `UserAvatar` component only fetched the userInfo from the redux user state store; however, we should also fetch from the currentUserInfo state if the `userID` prop equals the current user info id. This is because when we save an avatar, we only update the user avatar locally in redux in the `currentUserInfo` state not in the redux user state store. {F469346} This was causing an issue where when we saved the avatar and then navigated back it would take a while for the current user avatar to update since it was only looking at redux user state store which will update when it eventually detects this inconsistency.

In the past the `UserAvatar` component only fetched the userInfo from the redux user state store; however, we should also fetch from the currentUserInfo state if the `userID` prop equals the current user info id. This is because when we save an avatar, we only update the user avatar locally in redux in the `currentUserInfo` state not in the redux user state store. {F469346} This was causing an issue where when we saved the avatar and then navigated back it would take a while for the current user avatar to update since it was only looking at redux user state store which will update when it eventually detects this inconsistency.

In the past the `UserAvatar` component only fetched the userInfo from the redux user state store; however, we should also fetch from the currentUserInfo state if the `userID` prop equals the current user info id. This is because when we save an avatar, we only update the user avatar locally in redux in the `currentUserInfo` state not in the redux user state store. {F469346} This was causing an issue where when we saved the avatar and then navigated back it would take a while for the current user avatar to update since it was only looking at redux user state store which will update when it eventually detects this inconsistency.