Page MenuHomePhabricator

[lib] introduce SendReactionMessageRequest type to message types
ClosedPublic

Authored by ginsu on Nov 29 2022, 6:50 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 4, 10:36 PM
Unknown Object (File)
Mon, Nov 4, 3:49 PM
Unknown Object (File)
Mon, Nov 4, 3:49 PM
Unknown Object (File)
Mon, Nov 4, 8:21 AM
Unknown Object (File)
Mon, Oct 28, 7:32 AM
Unknown Object (File)
Oct 18 2024, 10:33 AM
Unknown Object (File)
Oct 12 2024, 4:16 AM
Unknown Object (File)
Sep 28 2024, 10:59 AM
Subscribers

Details

Summary

introduce SendReactionMessageRequest type to message types. This type will be needed in the reactionMessageCreationResponder

Test Plan

flow and this will be further tested in subsequent diffs

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu requested review of this revision.Nov 29 2022, 7:04 AM

Don't think this needed to be a separate diff

tomek added inline comments.
lib/types/message-types.js
549

What would it mean if a request with reaction = null was sent?

lib/types/message-types.js
549

I was thinking that if a reaction is null it would mean that the user unliked/unreacted to a message

This revision is now accepted and ready to land.Nov 30 2022, 3:19 PM
lib/types/message-types.js
549

This might be ok for now, but what will happen when a user has more reactions? Would null unset all of them? It seems like we should rethink our approach regarding removing reactions.

Thinking about it now is a good idea, because introducing API that has to be changed soon and requires checking client version increases complexity.

rebase with unsettingReaction field

rebase with action field