Content
@
0 reply
0 recast
2 reactions
rish
@rish
GM! took us a bit longer than expected but thanks to @shreyas-chorge, we now have an sdk for all farcaster read and write operations: github.com/neynarxyz/nodejs-sdk @pixel wrote some great guides on how you can get started! docs.neynar.com will keep adding new functionality, feedback is useful ππ½ πͺ
7 replies
20 recasts
69 reactions
Connor McCormick βοΈ
@nor
does it unify v1 and v2 response objects into a single shared type? Poked around but it's a big codebase
1 reply
0 recast
0 reaction
rish
@rish
good q. there is a helper function that converts v1 types to v2 so developers dont have to do that individually cc @shreyas-chorge
3 replies
0 recast
0 reaction
Connor McCormick βοΈ
@nor
ah nice, found that https://github.com/neynarxyz/nodejs-sdk/blob/main/src/neynar-api/utils/v1-to-v2-converters.ts I'd be interested in exploring the merits of converting to v2 by default for all endpoints. I have trouble imagining scenarios where v1 is better than v2 or where a builder wants inconsistency
1 reply
0 recast
0 reaction
rish
@rish
yeah we contemplated that but didn't do it by default in case folks wanted to make changes to existing workflows that used v1 endpoints. As our v2 endpoints mature, we expect most folks will use that
1 reply
0 recast
1 reaction
Connor McCormick βοΈ
@nor
makes sense. are threads supported on v2 yet? I think that's the big one
1 reply
0 recast
0 reaction
