LinkFarcasterUser should succeed if the FID is already associated with this user (no-op) but should fail if the FID is already associated with another user. We don't want the same FID associated with multiple Comm users.
Depends on D11412
Paths
| Differential D11413 Authored by varun on Mar 27 2024, 1:36 PM.
Details Summary LinkFarcasterUser should succeed if the FID is already associated with this user (no-op) but should fail if the FID is already associated with another user. We don't want the same FID associated with multiple Comm users. Depends on D11412 Test Plan Tried calling the RPC with an FID already associated with a different user and it failed. Tried calling with an FID associated with this user and it succeeded. Tried calling with an FID associated with no users and it succeeded.
Diff Detail
Event TimelineHerald added subscribers: tomek, ashoat. · View Herald TranscriptMar 27 2024, 1:36 PM2024-03-27 13:36:40 (UTC-7) Harbormaster completed remote builds in B27728: Diff 38391.Mar 27 2024, 1:52 PM2024-03-27 13:52:20 (UTC-7) varun added a child revision: D11423: [identity] unlink farcaster account RPC.Mar 27 2024, 4:50 PM2024-03-27 16:50:18 (UTC-7) This revision is now accepted and ready to land.Mar 27 2024, 11:58 PM2024-03-27 23:58:17 (UTC-7) Closed by commit rCOMM7e269eae587e: [identity] on linkFarcasterUser we should return an error if the FID already… (authored by varun). · Explain WhyMar 28 2024, 3:17 PM2024-03-28 15:17:26 (UTC-7) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 38391 services/identity/src/grpc_services/authenticated.rs
|