Content pfp
Content
@
0 reply
0 recast
0 reaction

Tony D’Addeo  pfp
Tony D’Addeo
@deodad
Request for feedback from frame devs: - give frames a way to respond with an error message that will be displayed to a user. - enables frames to give users quick feedback in response to user input https://warpcast.notion.site/Frames-Errors-ddc965b097d44d9ea03ddf98498597c6?pvs=74
26 replies
4 recasts
24 reactions

phil pfp
phil
@phil
3 replies
0 recast
26 reactions

Jason Goldberg Ⓜ️ 💜 pfp
Jason Goldberg Ⓜ️ 💜
@betashop.eth
like! we've been building our own
1 reply
0 recast
4 reactions

David Furlong pfp
David Furlong
@df
Is the value add over responding with a frame that the current input value can be preserved? performance? Is this an accessibility change? Perhaps this is possible via an accessible arial-label for images instead. Or is this a way for broken frames to communicate the errors back (not helpful for users)?
2 replies
0 recast
1 reaction

Colin Johnson 💭 pfp
Colin Johnson 💭
@cojo.eth
👋 hey Tony, any chance you can DC me? Have a question about frame transactions, horse said you may be able to help
0 reply
0 recast
1 reaction

jtgi pfp
jtgi
@jtgi
ship it i'd move what I could with /glass to this. Could delete some boring code and save the extra trip for img resolution would be a nice speed up (presumably). The flows I couldn't change are ones were I want to offer a follow up step based on the failure condition.
0 reply
0 recast
1 reaction

Blockheim pfp
Blockheim
@blockheim
From a ux/ui standpoint depending on the type of error you can also go for a message displayed under the input. It’ll feel more contextual imo
0 reply
0 recast
0 reaction

Daniel - Bountycaster pfp
Daniel - Bountycaster
@pirosb3
Took a look at the spec 💯. The only inconsistent aspect is returning JSON on error while a successful response remains OG tags.
0 reply
0 recast
0 reaction

Devin Conley pfp
Devin Conley
@conley
would this be supported in all responses? I think both standard frame views and also transaction urls could use this quick validation I wonder if it could be generalized beyond an error to just any message response. Some situations where it's not technically a 4xx but could be well handled via lightweight text message
0 reply
0 recast
0 reaction

Manan pfp
Manan
@manan
Same feedback as before, the dance between json and html isn’t ideal. Other than that, looks great!
0 reply
0 recast
0 reaction

Vladyslav Dalechyn pfp
Vladyslav Dalechyn
@dalechyn.eth
Love it
0 reply
0 recast
0 reaction

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
Works. Did with custom error frames that tell the user and redirect back to original frame Would give clients control over showing the error, no difference for frames devs basically since you handle error anyways?
1 reply
0 recast
0 reaction

TOM pfp
TOM
@subtlegradient
This will be abused to render arbitrary text instead of an image. I would absolutely abuse this
1 reply
0 recast
1 reaction

manan pfp
manan
@manangouhari
Love the direction but it would require the clients to very intelligently display the error. Can see this being a throwaway features if clients don't do justice by it.
1 reply
0 recast
0 reaction

Stephen Caudill pfp
Stephen Caudill
@mrmemes.eth
Please and thank you! Having a standardized way of returning error responses will save a lot of time.
0 reply
0 recast
1 reaction

Manuel pfp
Manuel
@manuelmaccou.eth
I’m into it if it’s faster than building custom error frames
0 reply
0 recast
1 reaction

mulf pfp
mulf
@mulf
Something inline would be much better than a whole additional request to generate an image!
0 reply
0 recast
1 reaction

Timur Badretdinov pfp
Timur Badretdinov
@destiner.eth
yuuuus please
0 reply
0 recast
0 reaction

Drew Beechler pfp
Drew Beechler
@drewbeechler
@hedges fyi
0 reply
0 recast
1 reaction

frolic pfp
frolic
@frolic
initial feedback: - thank you
0 reply
0 recast
1 reaction