Content
@
0 reply
0 recast
0 reaction
Vladyslav Dalechyn
@dalechyn.eth
Frog needs your opinion! https://github.com/wevm/frog/discussions/423
2 replies
0 recast
4 reactions
Johnson
@johnson
imo, the current flow is easier to maintain frames with minimal UI components. What we might really need is a way for the debug tools to warn or throw an error when the frame image size exceeds the limit. In my case, the image URLs worked fine in the local debug environment and failed when I deployed. Had this been warned about or thrown as an error in the development environment, I would have caught it earlier and followed the right approach. (I also faced this with input with a placeholder length of more than 32 bytes, which worked fine in debugging but failed after deployment. I don't know if this is specific to Warpcast and varies from client to client.)
0 reply
0 recast
0 reaction
