Page MenuHomePhabricator

[lib] Split `UpdateRelationshipMessageData` into `UpdateTraditionalMessageData` and `UpdateFarcasterMessageData`
ClosedPublic

Authored by atul on Thu, Apr 11, 8:05 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 27, 4:51 AM
Unknown Object (File)
Fri, Apr 26, 8:19 PM
Unknown Object (File)
Fri, Apr 26, 2:11 PM
Unknown Object (File)
Fri, Apr 26, 11:47 AM
Unknown Object (File)
Sun, Apr 21, 8:50 AM
Unknown Object (File)
Sun, Apr 21, 5:01 AM
Unknown Object (File)
Thu, Apr 18, 4:34 PM
Unknown Object (File)
Wed, Apr 17, 8:18 AM
Subscribers

Details

Summary

Pretty straightforward, the UpdateFarcasterMessageData variant includes creatorFID and targetFID.

Considered something like

+userIDsToFID: { +[userID: string]: string },

for consistency with FarcasterRelationshipRequest, but think this approach is cleaner and we don't need validators/etc to ensure that there are only two entries in userIDsToFID, etc.


Depends on D11624

Test Plan

flow + CI

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

atul published this revision for review.Thu, Apr 11, 8:06 PM
atul edited the summary of this revision. (Show Details)
tomek added inline comments.
lib/types/messages/update-relationship.js
15–24 ↗(On Diff #39070)
This revision is now accepted and ready to land.Fri, Apr 12, 2:39 AM
lib/types/messages/update-relationship.js
15–24 ↗(On Diff #39070)

Thanks for catching this!

This is safe to land since we don't have equivalent to https://github.com/CommE2E/comm/commit/7024301fcda748efefa900bd952cd8e127aac87d landed on master yet so these messages aren't currently getting created.

This revision was landed with ongoing or failed builds.Wed, Apr 17, 12:42 PM
This revision was automatically updated to reflect the committed changes.