Details
Details
- Reviewers
ashoat atul - Commits
- rCOMM41c71a9612a4: [web] introduce ThreadAvatar component
I was able to render all three avatar types: Emoji, Image, and ENS:
Emoji:
Image (by hardcoding const avatarInfo = { type: 'image', uri: 'https://picsum.photos/200' }):
ENS (by hardcoding const avatarInfo = { type: 'ens' } and the same ensAvatarURI I tested in D7262):
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
Comment Actions
Thanks for testing those scenarios in Test Plan. Question about API inline.
web/components/thread-avatar.react.js | ||
---|---|---|
27 ↗ | (On Diff #24532) | Are we not going to run into the same issue as with UserAvatar of having to make sure we're drilling threadInfo everywhere (I don't know, haven't taken a close look)? Should the prop just be threadID to match what we're doing for UserAvatars? |
web/components/thread-avatar.react.js | ||
---|---|---|
27 ↗ | (On Diff #24532) | Gotcha makes sense |