frames

It seems as though warpcast isn't posting to the `target` of `post` or `post_redirect` buttons, but is using the `fc:frame:post_url` instead - is this a bug or intentional? cc @horsefacts.eth @v

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

I work at the posts office

terminally.online

Senior prompt engineer. Shipped on farcaster: @larrybot, @qdau, @frames, @framesfun, /open-frames, farcasterchannels.com, farcaster.id, @mod, @search, @discove

You’re right, this is not implemented but made it into the docs. 

This is how it *should* work, though. We’ll update Warpcast to follow this spec.

/new-york by day 🗽 /untzuntz by night 😈 Fan of eating tacos and bringing people together, often at the same time 🌮

yeah that's what we're seeing too, but having a target on all buttons makes development significantly easier and simpler

I believe the docs on this are wrong, it’s very confusing. `target` is only respected when using action type `link` or `mint`. The other actions all use `post_url`.

I think I have raised this issue atleast 5 times... 😅 finally it got noticed.

software engineer /pinata 🎉
building tools for devs 

here's an example https://framesjs-test.vercel.app

this would immensely clean up my codebase 🙏

Ah, I had put in a PR to onchainkit about this https://github.com/coinbase/onchainkit/pull/130

Hopefully, this can be implemented soon as this opens the door for a much better DevX