Page MenuHomePhabricator

[lib] have landing send `fid` as a string and not a number
ClosedPublic

Authored by will on Wed, Apr 10, 11:19 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 22, 3:10 PM
Unknown Object (File)
Mon, Apr 22, 2:30 PM
Unknown Object (File)
Mon, Apr 22, 1:10 PM
Unknown Object (File)
Sun, Apr 21, 7:51 PM
Unknown Object (File)
Sun, Apr 21, 4:14 PM
Unknown Object (File)
Thu, Apr 18, 6:32 AM
Unknown Object (File)
Wed, Apr 17, 5:12 PM
Unknown Object (File)
Wed, Apr 17, 4:46 PM
Subscribers

Details

Summary

native expects a string but fid received is a number.

Context: https://linear.app/comm/issue/ENG-7679/type-mismatch-bug-in-farcaster-web-view-reactjs

Test Plan

flow check. Checked on native that receiving correct string fid after connecting my farcaster account

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

will requested review of this revision.Wed, Apr 10, 11:35 PM

toString on landing instead of after parse

will retitled this revision from [lib] convert `data.fid` which is a number to a string to [lib] have landing send `fid` as a string and not a number.Thu, Apr 11, 12:19 AM
will edited the summary of this revision. (Show Details)
will edited the test plan for this revision. (Show Details)
This revision is now accepted and ready to land.Thu, Apr 11, 4:10 AM

thanks for catching this @will. I thought I addressed this but looking at connect-farcaster.react.js now I can see I accidentally only toString() the farcaster auth url. Would you mind updating this diff to remove the toString() for the auth url? It's typed as a string already so doesn't make sense to toString() a string

will edited the test plan for this revision. (Show Details)

remove toString() on url which is already a string