Page MenuHomePhabricator

[web] update members modal to use the new tabs component
ClosedPublic

Authored by ginsu on Jan 4 2024, 1:13 AM.
Tags
None
Referenced Files
F3245648: D10521.diff
Thu, Nov 14, 7:49 PM
Unknown Object (File)
Wed, Nov 13, 4:27 PM
Unknown Object (File)
Mon, Nov 11, 9:29 AM
Unknown Object (File)
Wed, Nov 6, 1:35 PM
Unknown Object (File)
Thu, Oct 31, 4:22 AM
Unknown Object (File)
Thu, Oct 31, 4:22 AM
Unknown Object (File)
Thu, Oct 31, 4:22 AM
Unknown Object (File)
Thu, Oct 31, 4:22 AM
Subscribers

Details

Summary

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

Depends on D10520

Test Plan

Please see the demo video 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.
ginsu requested review of this revision.Jan 4 2024, 1:31 AM

Looks good

web/modals/threads/members/members-modal.react.js
26–35 ↗(On Diff #35187)

Same feedback as rest of the stack, but the id and headers seem redundant. Let me know if there's something I'm missing?

115–121 ↗(On Diff #35187)

Wouldn't hurt to sneak a React.useMemo here..

This revision is now accepted and ready to land.Jan 4 2024, 12:57 PM
web/modals/threads/members/members-modal.react.js
26–35 ↗(On Diff #35187)

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

address comments + rebase before landing