Page MenuHomePhabricator

[web] Implement callbacks modifying navigation from `ChatThreadComposer`
ClosedPublic

Authored by jacek on Jul 7 2022, 2:15 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Apr 28, 3:57 AM
Unknown Object (File)
Wed, Apr 24, 12:47 PM
Unknown Object (File)
Apr 4 2024, 7:17 PM
Unknown Object (File)
Apr 3 2024, 8:23 PM
Unknown Object (File)
Apr 3 2024, 1:55 AM
Unknown Object (File)
Apr 1 2024, 10:28 PM
Unknown Object (File)
Mar 31 2024, 10:01 PM
Unknown Object (File)
Mar 31 2024, 12:13 PM

Details

Summary

Introduce implementation of functions modifying navigation state after adding/removing user to list of selected and after exiting thread creation mode.

Test Plan

The component is not used in app yet. Tested it by performing different sequences of operations on users after introducing chat creation view in next diffs.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jul 19 2022, 11:48 AM
web/chat/chat-thread-composer.react.js
59 ↗(On Diff #14392)

We could move this before the call to dispatch(...) like we do in onRemoveUserFromSelected?

tomek added inline comments.
web/chat/chat-thread-composer.react.js
52–55 ↗(On Diff #14392)

Why do we check this? In dispatch, we're not using userInfo, but maybe this check protects us against some scenarios

web/chat/chat-thread-composer.react.js
52–55 ↗(On Diff #14392)

Thanks for catching. I probably left it by accident after some changes. Selected user IDs are always from otherUserInfos so it's impossible for this condition to return here. Removing it will make dependency list shorter

Adress Tomek's and Atul's feedback