Page MenuHomePhabricator

[native] switch all thread avatars to use ThreadAvatar component instead of Avatar
ClosedPublic

Authored by ginsu on Mar 30 2023, 3:13 PM.
Tags
None
Referenced Files
F3520222: D7263.diff
Sun, Dec 22, 11:38 PM
Unknown Object (File)
Fri, Dec 6, 9:54 PM
Unknown Object (File)
Thu, Dec 5, 8:38 PM
Unknown Object (File)
Thu, Dec 5, 8:38 PM
Unknown Object (File)
Thu, Dec 5, 8:38 PM
Unknown Object (File)
Wed, Dec 4, 3:34 AM
Unknown Object (File)
Wed, Dec 4, 3:33 AM
Unknown Object (File)
Tue, Nov 26, 7:14 PM
Subscribers

Details

Summary

Now that we have ThreadAvatar we should render that for thread avatars instead of Avatar

Depends on D7262

Test Plan

Tested that all the thread avatars are still able to be rendered correctly for all three avatar types (emoji, image, and ens)

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu requested review of this revision.Mar 30 2023, 3:29 PM
ashoat requested changes to this revision.Mar 30 2023, 5:50 PM

In all of these cases we already have the threadInfo. Instead of requiring ThreadAvatar to fetch it again, should we just pass it in directly?

This revision now requires changes to proceed.Mar 30 2023, 5:50 PM

address ashoat's comments

This revision is now accepted and ready to land.Mar 31 2023, 5:30 AM