Page MenuHomePhabricator

[lib] Update pending thread type based on selected members
ClosedPublic

Authored by tomek on Mon, Sep 30, 5:21 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Sep 30, 6:00 AM
Unknown Object (File)
Mon, Sep 30, 6:00 AM
Unknown Object (File)
Mon, Sep 30, 5:59 AM
Unknown Object (File)
Mon, Sep 30, 5:59 AM
Subscribers

Details

Summary

Every time a list of selected users change check whether they support thick threads and update the type accordingly. Checking the support is an asynchronous operation which causes a lot of changes in other places.

https://linear.app/comm/issue/ENG-9393/update-pending-thread-type-based-on-selected-members

Depends on D13489

Test Plan

Modify useUserSupportThickThread so that it returns false for some users. Check if the thread type is determined correctly on native and web.

Tested following scenarios

  1. Searching for a user on native with useUserSupportThickThread modified to return false for some users
  2. Searching for a user on native without modifications to useUserSupportThickThread
  3. Searching for a user on web with useUserSupportThickThread modified to return false for some users
  4. Searching for a user on web without modifications to useUserSupportThickThread
  5. Composing a thread on native with useUserSupportThickThread modified to return false for some users
  6. Composing a thread on native without modifications to useUserSupportThickThread
  7. Composing a thread on web with useUserSupportThickThread modified to return false for some users
  8. Composing a thread on web without modifications to useUserSupportThickThread

For each of these verified that the thread type is displayed correctly and that sending a message results in the creation of the correct thread type.

Diff Detail

Repository
rCOMM Comm
Branch
publish-personal-2
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

tomek requested review of this revision.Mon, Sep 30, 5:37 AM

Can you update the test plan to cover all of these scenarios?

  1. Searching for a user on native with useUserSupportThickThread modified to return false for some users
  2. Searching for a user on native without modifications to useUserSupportThickThread
  3. Searching for a user on web with useUserSupportThickThread modified to return false for some users
  4. Searching for a user on web without modifications to useUserSupportThickThread
  5. Composing a thread on native with useUserSupportThickThread modified to return false for some users
  6. Composing a thread on native without modifications to useUserSupportThickThread
  7. Composing a thread on web with useUserSupportThickThread modified to return false for some users
  8. Composing a thread on web without modifications to useUserSupportThickThread
This revision is now accepted and ready to land.Mon, Sep 30, 6:01 AM

Can you update the test plan to cover all of these scenarios?

  1. Searching for a user on native with useUserSupportThickThread modified to return false for some users
  2. Searching for a user on native without modifications to useUserSupportThickThread
  3. Searching for a user on web with useUserSupportThickThread modified to return false for some users
  4. Searching for a user on web without modifications to useUserSupportThickThread
  5. Composing a thread on native with useUserSupportThickThread modified to return false for some users
  6. Composing a thread on native without modifications to useUserSupportThickThread
  7. Composing a thread on web with useUserSupportThickThread modified to return false for some users
  8. Composing a thread on web without modifications to useUserSupportThickThread

Sure!