Page MenuHomePhabricator

[native] Consume `useAvailableThreadMemberActions` in `native/ThreadSettingsMember`
ClosedPublic

Authored by atul on May 6 2024, 1:13 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 24, 1:05 AM
Unknown Object (File)
Sun, Dec 22, 8:28 PM
Unknown Object (File)
Sun, Dec 22, 8:28 PM
Unknown Object (File)
Sun, Dec 22, 8:28 PM
Unknown Object (File)
Sun, Dec 22, 8:27 PM
Unknown Object (File)
Sun, Dec 22, 8:27 PM
Unknown Object (File)
Fri, Nov 29, 2:40 PM
Unknown Object (File)
Nov 26 2024, 3:42 AM
Subscribers
None

Details

Summary

Similar to D11913, but for ThreadSettingsMember.

This was last usage of getAvailbleThreadMemberAction, so we also go ahead and remove it.


Depends on D11913

Test Plan

flow + close reading for now

Logged value of getAvailbleThreadMemberAction and useAvailableThreadMemberActions and ensured value was the same. Assuming the logic in ThreadSettingsMember that works with value is and remains correct.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable