frames-devs

1) @frames, CC @stephancill @df I'm diving a bit deeper into some more (complex?) conditional logic. My issue is that, given the scenario below, I'm unable to determine in the reducer when loading pg3 which btn is clicked on pg2, ie `doB` or `doC`, because all I have available is the idx, which is `1` for both/either?

Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

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

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

Hmmm, I did try this, but didn't see the modified state in the next frame, and assumed it would only accept state updates via the reducer, but i'll try that again...

` <FrameContainer {...{ postUrl, previousFrame, pathname }} state={{ ...state, notEligible: true }}>`

You can modify the state that will be available in the next frame in your component that returns the next FrameContainer

So when returning frame B, include some additional context in your state e.g. <FrameContainer state={…state, subpage: “B”}

Which you can then check in your reducer

Okay, thanks @df @stephancill it looks like directly manipulating the state object as it's passed into the <FrameContainer /> does the trick.  I avoided pushing ahead with this pattern thinking all state modification should be restricted to the reducer redux-style. Thanks for the responsiveness!

yeah thats what the state should solve; you should store whatever additional context you need in the reducer state