Page MenuHomePhabricator

[native] introduced useCanCreateReactionFromMessage function to reaction message utils
ClosedPublic

Authored by ginsu on Dec 12 2022, 1:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 28, 3:57 AM
Unknown Object (File)
Thu, Nov 28, 1:13 AM
Unknown Object (File)
Nov 24 2024, 7:43 AM
Unknown Object (File)
Nov 24 2024, 7:41 AM
Unknown Object (File)
Nov 24 2024, 7:24 AM
Unknown Object (File)
Nov 24 2024, 6:04 AM
Unknown Object (File)
Nov 8 2024, 5:16 PM
Unknown Object (File)
Nov 8 2024, 5:16 PM
Subscribers

Details

Summary

introduced useCanCreateReactionFromMessage function to reaction message utils. useCanCreateReactionFromMessage does several checks if the user can send a reaction message and depending on the result of those checks will display the react option to the message tooltip. The function checks if the message has been realized (only realized messages have an id), it also checks if the reaction message creator is currently is not blocked by the other target message creator, and it also checks if the reaction message creator has permission to voice in the thread


Depends on D5780
Linear Task: ENG-2246

Test Plan

Please watch the demo videos to see the changes i made (in the middle of the demo, there is some hangtime where I am waiting for simulator to reconnect, feel free to fast forward through that part):

Demos to show scenario where a blocked/blocker pair of users is in a group chat:

Dan's (blocker) POV:

Ryan's (blocked) POV:

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu requested review of this revision.Dec 12 2022, 1:14 PM

Seems logical to me after watching the demo

tomek added a reviewer: ashoat.

Accepting because the code looks ok

native/chat/reaction-message-utils.js
94 ↗(On Diff #19293)

We can return a relationship to make this more efficient

102–104 ↗(On Diff #19293)

Are we sure that we want to block reactions depending on the relationship? I guess in personal chats it makes sense, but I'm not sure about the public ones. @ashoat do you have an opinion on this?

Regardless, we have to make sure that this is consistent with server and web logic.

ashoat requested changes to this revision.Dec 13 2022, 4:07 PM

Back to you with questions

native/chat/reaction-message-utils.js
102–104 ↗(On Diff #19293)

Hmm... I'm also curious about how we normally treat a scenario where a blocked/blocker pair of users is in a group chat.

@ginsu, two questions for you about that scenario:

  1. Can the blocked user see the blocker's messages?
  2. Can the blocked user start a thread on the blocker's messages?

Regardless, we have to make sure that this is consistent with server and web logic.

Good reminder!!

This revision now requires changes to proceed.Dec 13 2022, 4:07 PM
ginsu edited the test plan for this revision. (Show Details)

addressed feedback

native/chat/reaction-message-utils.js
102–104 ↗(On Diff #19293)

Updated the test plan to have a demo to show this scenario but the TLDR is this:

  1. The blocked user CAN see the blocker's message
  2. The blocked user CANNOT start a thread on the blocker's method

I tried making the logic for the react tooltip option consistent with what the thread tooltip option has, but let me know if we should be doing something else!

Cool!! Please make sure privacy/blocking logic is consistent across web/native/keyserver

Looks good

Please respond to following before landing:

Cool!! Please make sure privacy/blocking logic is consistent across web/native/keyserver

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

changed variable names to be more descriptive

Cool!! Please make sure privacy/blocking logic is consistent across web/native/keyserver

Found an inconsistency in the privacy/blocking logic in the keyserver and updated D5749 to resolve the inconsistency