Page MenuHomePhabricator

[web] house the thread list in a panel component
AcceptedPublic

Authored by ginsu on Jan 4 2024, 3:40 AM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 31 2024, 2:25 AM
Unknown Object (File)
Oct 31 2024, 2:25 AM
Unknown Object (File)
Oct 31 2024, 2:24 AM
Unknown Object (File)
Oct 3 2024, 10:51 AM
Unknown Object (File)
Sep 18 2024, 12:55 AM
Unknown Object (File)
Sep 18 2024, 12:55 AM
Unknown Object (File)
Sep 18 2024, 12:54 AM
Unknown Object (File)
Sep 8 2024, 10:11 PM
Subscribers

Details

Reviewers
atul
inka
Summary

PLEASE NOTE THAT THIS DIFF AND SUBSEQUENT DIFFS IN THIS STACK WILL NOT BE LANDED UNTIL MORE OF THE REDESIGN IS READY SINCE THIS WILL CAUSE REGRESSIONS IN PROD

This diff updates the chat component to use the panel component I introduced earlier. To make things easy to review I only included the changes for the thread list; however, in subsequent diffs I will bring back the message list and house it in this same panel component

Linear task: https://linear.app/comm/issue/ENG-5935/chat-thread-list-ui-redesign

Depends on D10527

Test Plan

Please see a the demo video below:

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

web/chat/chat.css
1–6

Confirmed that this style was not being used anywhere

web/chat/chat.react.js
43

We move this here so both ChatTabs and chatList have context on the the thread list provider

ginsu edited the test plan for this revision. (Show Details)
ginsu added reviewers: atul, inka.
ginsu edited the summary of this revision. (Show Details)
ginsu requested review of this revision.Jan 4 2024, 3:58 AM
atul added inline comments.
web/chat/chat.css
1–6

FWIW most IDEs can automatically detect unused CSS selectors. Might be heavy weight to add a CSS stylecheck to CI, but flipping setting on in your IDE might help catch these early?

web/chat/chat.react.js
42–45

Would definitely be good to memoize this

This revision is now accepted and ready to land.Jan 4 2024, 1:55 PM
web/chat/chat.react.js
42–45

It looks like on line 49 we are memoizing this component, is it still necessary to wrap this in a useMemo?

web/chat/chat.css
1–6

Took 2 seconds to run, so put up the following with some obvious selectors that can be removed: https://phab.comm.dev/D10547

There are definitely more, but there were string matches in the codebase so I just unstaged those to keep this as quick as possible.