Multiple actions in handler not receiving updated state about boardgame.io

[nicolodavis]

When you say the game state is changed, you mean you are able to see the new state on the Debug UI? Which props do you find are stale? What is this callback you are referring to (did you mean click handler)?

[michaelmior]

Yes, I meant click handler. Specifically, the game state is stale. For example, I have an action called selectDie and in that action, I log the new state produced. Immediately after calling that action, I see the state has correctly changed, but this.props.G still refers to the old state.

[nicolodavis]

Do you have a link to your code? I can take a look and see what's going on.

[michaelmior]

Thanks! Unfortunately, the code is a bit of a mess now since I just started working on the project this afternoon. Here is the line where I specifically call my move. The logging statement after shows that the game state is stale.

[nicolodavis]

reduxjs/react-redux#748 should answer your question.

Also, I would recommend keeping click handlers fairly simple. There shouldn't be much game logic in there. Your game might also benefit from the upcoming support for phases.

[michaelmior]

@nicolodavis Yes, I agree that the handler is getting too complex. I've been watching the phases support and I think that would likely make things much cleaner. Is it currently possible to call a move (or endTurn) from within another move?

[nicolodavis]

Calling an action from a reducer (move handler) is generally considered an anti-pattern.

I think the phases support should help with this. There are hooks to automatically end a phase when a particular condition is met.

I'll add something similar for ending turns.

[michaelmior]

Thanks! This is just a fun side project so I'll probably just wait until phases support lands.