Page MenuHomePhabricator

[native] toggle reaction action in onPressReact function
ClosedPublic

Authored by ginsu on Dec 12 2022, 8:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 15 2024, 1:48 PM
Unknown Object (File)
Nov 15 2024, 1:41 PM
Unknown Object (File)
Nov 15 2024, 1:33 PM
Unknown Object (File)
Nov 13 2024, 5:14 AM
Unknown Object (File)
Nov 8 2024, 10:00 AM
Unknown Object (File)
Nov 8 2024, 10:00 AM
Unknown Object (File)
Nov 7 2024, 4:03 PM
Unknown Object (File)
Nov 7 2024, 4:03 PM
Subscribers

Details

Summary

toggle reaction action in onPressReact function. Hard setting reactionInput right now but will changing this when we expand from just sending likes to more reactions.

Also, right now the tooltip option does not change from '๐Ÿ‘', but will be addressing this in a subsequent diff


Linear Task: ENG-2243
Depends on D5854

Test Plan

Please watch the demo video to see how the toggle works:

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu edited the test plan for this revision. (Show Details)
ginsu added reviewers: atul, tomek, rohan.
ginsu requested review of this revision.Dec 12 2022, 8:55 PM

I think that we have to introduce some animations so that the UI doesn't jump when a reaction is added / removed, but that will be complicated so it should be a separate task which we can prioritize later.

native/chat/reaction-message-utils.js
45 โ†—(On Diff #19301)

Should we use reactionInput here?

In D5854#175269, @tomek wrote:

I think that we have to introduce some animations so that the UI doesn't jump when a reaction is added / removed, but that will be complicated so it should be a separate task which we can prioritize later.

Totally agree, some of the animations are a bit clunky and need to be fine-tuned, but I think it will be better to address that in a separate task for the future

This revision is now accepted and ready to land.Dec 15 2022, 9:24 AM

You should never reference a task without linking it. @ginsu, please create and link the task you're describing before landing this diff

In D5854#175378, @ginsu wrote:
In D5854#175269, @tomek wrote:

I think that we have to introduce some animations so that the UI doesn't jump when a reaction is added / removed, but that will be complicated so it should be a separate task which we can prioritize later.

Totally agree, some of the animations are a bit clunky and need to be fine-tuned, but I think it will be better to address that in a separate task for the future

Follow up task