Page MenuHomePhabricator

[web][native] update `InputStateContainer` logic for sending multimedia messages
ClosedPublic

Authored by kamil on Fri, Sep 13, 4:27 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Sep 17, 12:28 PM
Unknown Object (File)
Tue, Sep 17, 2:45 AM
Unknown Object (File)
Mon, Sep 16, 2:36 AM
Unknown Object (File)
Fri, Sep 13, 8:44 AM
Unknown Object (File)
Fri, Sep 13, 8:44 AM
Unknown Object (File)
Fri, Sep 13, 8:43 AM
Subscribers

Details

Summary

ENG-8424.

This makes updates code to use one hok on both platforms which handles both thick and thin threads, avoids hacking logic on both InputStateContainer.

Depends on D13331

Test Plan
  1. Sending multimedia.
  2. Multimedia statuses.
  3. Multimedia retries.
  4. Creating thread where first message is multimedia.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Fri, Sep 13, 4:42 AM
bartek added inline comments.
web/input/input-state-container.react.js
540–543 ↗(On Diff #44149)

Is this still used anywhere in this func? I see you moved this into the useInputStateContainerSendMultimediaMessage() hook in the previous diff

This revision is now accepted and ready to land.Fri, Sep 13, 6:19 AM
tomek added inline comments.
web/input/input-state-container.react.js
548 ↗(On Diff #44149)

What does it mean to be a legacy? Are we planning to update the approach?

web/input/input-state-container.react.js
548 ↗(On Diff #44149)

We have two ways of calling the create_multimedia_message keyserver endpoint:

  • the new one which accepts mediaMessageContents - used on native, according to D5127 and D5191 it also supports videos
  • the "legacy" one which accepts mediaIDs - used on web

I guess we'll stop using the legacy one when we implement video uploads for web