Page MenuHomePhabricator

[lib] Introduce bare minimum `messageTypes.UPDATE_RELATIONSHIP`
ClosedPublic

Authored by atul on Mar 28 2024, 7:40 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 21, 2:46 AM
Unknown Object (File)
Thu, Nov 21, 2:46 AM
Unknown Object (File)
Oct 22 2024, 2:15 PM
Unknown Object (File)
Oct 22 2024, 1:15 PM
Unknown Object (File)
Oct 22 2024, 8:35 AM
Unknown Object (File)
Oct 22 2024, 8:35 AM
Unknown Object (File)
Oct 22 2024, 8:35 AM
Unknown Object (File)
Oct 22 2024, 8:35 AM
Subscribers

Details

Summary

Basically fill out update-relationships with contents of legacy-update-relationships with additional farcaster_mutual operation.

Based on following commit from hackathon branch: https://github.com/CommE2E/comm/commit/8dd3e3339b8ac1435bc79064c2a9253bb07334e8


Depends on D11436

Test Plan

flow/things work as expected in subsequent diffs

Diff Detail

Repository
rCOMM Comm
Branch
arcpatch-D11438 (branched from master)
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

atul requested review of this revision.Mar 28 2024, 7:55 AM
This revision is now accepted and ready to land.Mar 28 2024, 8:24 PM

Rather than rebasing and updating stack, it should be fine to land as-is and make modifications in follow-up diffs since this message type is not yet available to prod clients.

Developers can delete any messageTypes.UPDATE_RELATIONSHIP messages they may create by filtering on type 22 from their dev DB.

This revision was landed with ongoing or failed builds.Apr 4 2024, 12:29 PM
This revision was automatically updated to reflect the committed changes.