Page MenuHomePhabricator

[lib] Process blob holders in DM ops
ClosedPublic

Authored by bartek on Sep 20 2024, 6:30 AM.
Tags
None
Referenced Files
F3364891: D13411.diff
Mon, Nov 25, 5:41 AM
Unknown Object (File)
Wed, Nov 20, 10:36 AM
Unknown Object (File)
Wed, Nov 20, 10:36 AM
Unknown Object (File)
Wed, Nov 20, 10:35 AM
Unknown Object (File)
Wed, Nov 20, 10:35 AM
Unknown Object (File)
Wed, Nov 13, 10:54 PM
Unknown Object (File)
Wed, Nov 13, 6:32 PM
Unknown Object (File)
Wed, Nov 13, 6:25 AM
Subscribers

Details

Summary

Added a hook that dispatches holder processing action as a result of DM ops.

Depends on D13407, D13409, D13410

Test Plan

Created dummy blob op in dm-ops/change-thread-settings for creating and removing a holder.
Watched Redux Devtools and Blob HTTP traffic to confirm that holders are established and removed correctly.
Also tested with D13413 test plan

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Sep 20 2024, 7:09 AM
lib/actions/holder-actions.js
141–142

Why do we want until getAuthMetadata() resolves before starting createBlobHolderGenerator()?

kamil added inline comments.
lib/actions/holder-actions.js
7–8

can be merged

129

nit: I prefer this but since this is not a convention, I've seen both it codebase it's fine 😆

163

are you sure this will always be defined?

This revision is now accepted and ready to land.Sep 23 2024, 1:16 AM
lib/actions/holder-actions.js
129

We cannot destructure undefined. And I prefer to invariant as late as possible

141–142

After refactor it's no longer this way

163

Good catch

This revision was automatically updated to reflect the committed changes.