Page MenuHomePhabricator

[web] upate emoji avatar selection modal to use new tabs component
ClosedPublic

Authored by ginsu on Jan 4 2024, 12:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 3, 12:02 PM
Unknown Object (File)
Sat, Sep 14, 9:18 PM
Unknown Object (File)
Sat, Sep 14, 9:18 PM
Unknown Object (File)
Sat, Sep 14, 9:18 PM
Unknown Object (File)
Sat, Sep 14, 9:18 PM
Unknown Object (File)
Aug 23 2024, 10:46 AM
Unknown Object (File)
Aug 18 2024, 5:49 AM
Unknown Object (File)
Jul 19 2024, 4:13 AM
Subscribers

Details

Summary

This diff updates the emoji avatar selection modal to use the new tab components. Since we decoupled the tabs from the tab content with this new tab component, the emoji avatar selection modal now needs to be responsible for rendering the correct tab content.

Depends on D10516

Test Plan

Please see the demo video below to confirm that there are no regressions

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu edited the test plan for this revision. (Show Details)
ginsu added reviewers: atul, inka.
Harbormaster returned this revision to the author for changes because remote builds failed.Jan 4 2024, 1:00 AM
Harbormaster failed remote builds in B25470: Diff 35184!
ginsu requested review of this revision.Jan 4 2024, 1:01 AM

will make sure ci passes before landing

Seems reasonable, thanks for including the video in the Test Plan!

web/avatars/emoji-avatar-selection-modal.react.js
25–28 ↗(On Diff #35184)

Would it make sense to use "Emoji" for both? Creating a whole separate object that only really contains one string seems like it might be overkill? Don't feel strongly though, def fine to land as is.

This revision is now accepted and ready to land.Jan 4 2024, 12:41 PM
web/avatars/emoji-avatar-selection-modal.react.js
25–28 ↗(On Diff #35184)

I made the header field a type of React.Node. I did this so that if we ever wanted to add other elements to the header component we could just pass in a react component as the value of this field. I could imagine us wanting to put icons in the future or doing other things and I thought this would be the best way to make the tabs component as flexible/future proof as possible