frames-devs

Looking for feedback on frames.js
 
What can we do better and what should we work on next?

If you could wave a magic wand and solve a problem related to making frames, what would it be?

answers are very helpful and appreciated 🙏

the simplest way to make /frames.
Ask for help in /frames-devs.
Docs at framesjs.org

I will try to report these on github, but I used it last night for the first time, and here are my notes:
- `value` should be an optional type on transaction
- You should be able to opt out of Hub fetches, some like getUserData takes up to 3s sometimes
- Some useful internal utils are not exported (node-server-helpers)

CTO & Full Stack Developer at @rmrk. Building modular NFTs with truly on-chain composability JS maxi, tea, advaita vedanta, psychonaut
https://x.com/Yuripetusko

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

yes exactly, getUserData can be quite slow, and with 5s timeout it's often unreasonable to expect frame to return something in that time with ~6 hub requests from hub context middleware. Had to write my own simple middleware for only the data that I need

thanks for the feedback!

- optional transaction value will go out in the next release
- hub fetches are opt-in in the new api, are you referring to splitting the hub context middleware into verification and getUserData?
- will consider exporting some of the internal utils