Page MenuHomePhabricator

[lib] Dispatch processNewUserIDsActionType
ClosedPublic

Authored by inka on Jun 6 2024, 3:49 AM.
Tags
None
Referenced Files
F3498966: D12329.id41106.diff
Thu, Dec 19, 9:59 PM
F3498944: D12329.id41035.diff
Thu, Dec 19, 9:57 PM
F3496764: D12329.diff
Thu, Dec 19, 2:43 PM
F3495795: D12329.id41683.diff
Thu, Dec 19, 9:59 AM
F3495794: D12329.id41106.diff
Thu, Dec 19, 9:59 AM
F3495793: D12329.id41039.diff
Thu, Dec 19, 9:59 AM
F3495792: D12329.id41035.diff
Thu, Dec 19, 9:59 AM
F3495771: D12329.id.diff
Thu, Dec 19, 9:58 AM
Subscribers

Details

Summary

issue: [[https://linear.app/comm/issue/ENG-8190/[inka][june]-userstore-syncing-stop-processing-data-from-secondary | ENG-8190]]
After extracting user ids from server message we want to dispatch processNewUserIDsActionType to create entries for these ids in the user store. Then, UserInfosHandler will fetch missing user infos.

Test Plan

Tested that the action is dispatched both for socket messages and http api responses

Diff Detail

Repository
rCOMM Comm
Branch
inka/userStore
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

inka requested review of this revision.Jun 6 2024, 4:05 AM
tomek added inline comments.
lib/socket/user-infos-handler.react.js
14–35

Up to you, but we can useDispatch() here instead of passing the value as a prop

This revision is now accepted and ready to land.Jun 6 2024, 4:18 AM
inka planned changes to this revision.Jun 6 2024, 5:03 AM

Actually I should avoid dispatching the action if userIDs is empty. This results in a lot of unnecessary actions, mostly from PONG message

Stop dispatching if array empty

This revision is now accepted and ready to land.Jun 6 2024, 5:08 AM
lib/socket/user-infos-handler.react.js
14–35

Personally I think this would be cleaner

This revision was automatically updated to reflect the committed changes.