Content pfp
Content
@
0 reply
0 recast
0 reaction

Johnson pfp
Johnson
@johnson
Is there a debugger for cast-actions like Warpcast frame validator or @frames debugger or @frog-dev devtools? How do you all test cast actions locally?
1 reply
0 recast
1 reaction

Andrei O. pfp
Andrei O.
@andrei0x309
There's not much to test, action can either send messages back or frame. So for messages, there's nothing to test because that will be just a toast on Waprcast. And for the frame, you have the validators you enumerated before. In a worst-case scenario, you would use a test fid to test live, on warpcast, you just need to install the action. And you can do that with the URL for installing actions ex: https://warpcast.com/~/add-cast-action?url=https://api.yup.io/fc-actions/cross-post On Warpcast validators are only for composer-actions, and frames not for simple actions, but like I said don't see a good reason for them.
1 reply
0 recast
1 reaction

Johnson pfp
Johnson
@johnson
That makes sense 👍. Thought about this when a small difference led me on a wild goose chase. When hitting a frame for the first time from a cast, the state isn’t included. However, when doing it from the cast action, it's included. (I was using from.fm . Not sure if that's specific to the framework.)
1 reply
0 recast
1 reaction