Page MenuHomePhabricator

[keyserver] reply on farcaster with invite link
ClosedPublic

Authored by will on Oct 23 2024, 11:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Unknown Object (File)
Mon, Dec 16, 9:54 PM
Subscribers

Details

Summary

Putting this diff for review. Currently debugging our invalid signerUUID. This diff replies on farcaster with the invite link

Depends on D13784

Test Plan

Tested with my local iOS simulator comm app. I grabbed the invite link posted to warpcast and pasted it to my safari. Was able to successfully join new communities and/or sidebars

Diff Detail

Repository
rCOMM Comm
Branch
farcaster_bot
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

will published this revision for review.Oct 23 2024, 11:51 PM
will added inline comments.
keyserver/src/responders/farcaster-webhook-responders.js
262 ↗(On Diff #45368)

Definitely wanted to get an opinion on what we might change this to

keyserver/src/responders/farcaster-webhook-responders.js
262 ↗(On Diff #45368)

We shouldn't hardcode the link - instead, we should use inviteLinkURL function.

will planned changes to this revision.Oct 24 2024, 6:23 AM

Planning changes based on Tomek's feedback

keyserver/src/responders/farcaster-webhook-responders.js
266 ↗(On Diff #45368)
keyserver/src/responders/farcaster-webhook-responders.js
262 ↗(On Diff #45368)

review feedback and changes

will added inline comments.
keyserver/src/responders/farcaster-webhook-responders.js
288–290 ↗(On Diff #45488)
292–294 ↗(On Diff #45488)

Curious if I should move the neynarConfig higher in the code and exit early if missing or let the community + sidebar creation code run through

ashoat requested changes to this revision.Oct 30 2024, 2:56 PM
ashoat added inline comments.
keyserver/src/responders/farcaster-webhook-responders.js
286 ↗(On Diff #45488)

Why do we wait until this point to start this promise?

288–290 ↗(On Diff #45488)

Please keep all lines to a max of 80 chars

292–294 ↗(On Diff #45488)

I'd probably move it higher

296 ↗(On Diff #45488)
  1. Typo
  2. If the condition on line 292 passes, doesn't that mean we have a neynarClient?
297 ↗(On Diff #45488)

Doesn't the condition on line 292 mean we have a signerUUID?

302 ↗(On Diff #45488)

Do we need the question mark?

This revision now requires changes to proceed.Oct 30 2024, 2:56 PM
keyserver/src/responders/farcaster-webhook-responders.js
286 ↗(On Diff #45488)

Addressed by moving up higher as a promise

292–294 ↗(On Diff #45488)

Ended up moving it higher as a promise but kept the missing_signer_uuid check at the same spot as I don't think we're expecting this to happen

297 ↗(On Diff #45488)

This is correct. Removing ?

302 ↗(On Diff #45488)

Looks like we do. Flow complains if I remove it and says its type is void | NeynarPostCastResponse

keyserver/src/responders/farcaster-webhook-responders.js
296 ↗(On Diff #45488)

Confused. 292 is for neynarConfig right? I found several examples in the codebase of using it as neynarClient?.method

ashoat added inline comments.
keyserver/src/responders/farcaster-webhook-responders.js
284–293 ↗(On Diff #45496)

Nit: probably best to group these two awaits into a single Promise.all. The fewer awaits at the top level the better

296 ↗(On Diff #45488)

Oops yeah I confused the two

This revision is now accepted and ready to land.Oct 30 2024, 7:11 PM
will marked an inline comment as done.Oct 31 2024, 6:00 AM
This revision was automatically updated to reflect the committed changes.
will marked an inline comment as not done.