Content
@
https://warpcast.com/~/channel/frames-v2
0 reply
0 recast
0 reaction
Colin
@colin
Feedback on frames v2 docs & specifications after working on the Paragraph v2 frame: - events are a bit confusing: some code examples reference `Farcaster.events.on` and others reference `sdk.on` - "see full example" Github link is broken on the specs page - primaryButtonClick code example at the bottom is wrong; should be `primaryButtonClicked` - would prefer hooks over callbacks - provider configuration is confusing: connected set to true by default? immediately tries to connect on provider setup? I had to change a handful of things to get it working - overall specification is clear but a few things could be a bit clearer (SetPrimaryButton -> what does hidden/enabled do? There's also no mention of loading but there is a loading param in the code) - unclear why SDK needs to be lazy-loaded using a dynamic component vs just doing nothing on the server-side - debugging is a struggle: https://warpcast.com/colin/0x61b315b3
3 replies
4 recasts
20 reactions
Colin
@colin
cc @horsefacts.eth @deodad @dwr.eth @v
1 reply
0 recast
1 reaction
horsefacts 🚂
@horsefacts.eth
thanks, all great feedback. some of these things are fixed but not in the docs yet. some tactical stuff for your frame: > provider configuration is confusing: connected set to true by default? immediately tries to connect on provider setup? I had to change a handful of things to get it working sounds like you're using the copy-pasted connector from early examples, use @farcaster/frame-wagmi-connector instead > overall specification is clear but a few things could be a bit clearer (SetPrimaryButton -> what does hidden/enabled do? There's also no mention of loading but there is a loading param in the code) primary button is not really supported yet, don't use it. > unclear why SDK needs to be lazy-loaded using a dynamic component vs just doing nothing on the server-side this is not necessary any more in latest Frame SDK
1 reply
0 recast
2 reactions
