Actions not passed to connected component on server.

I am not sure if this is done by design, but having the app setup as instructed in the structuring your app and server rendering sections of the guide my app on the server breaks. I am getting and error cannot real modals of undefined error when trying to access actions.modals.openModal in an onClick handler.

const { actions } = useOvermind(); In render

return (
  <div  onClick={actions.sidebars.toggleDrawer}></div>
)

I could set actions to a default {} but wanted to make sure I wasn’t doing anything wrong.

Huge fan of this library coming from Baobab and Celebral! Great Work!

[christianalfoni]

Ah, yeah, no it does not fire up. The reason is that it is considered a side effect on the server that you might not want. Like with tests, you do not want onInitialize to fire up as it would cause a side effect to your tests.

But what I suggest you do here is to rather create your own action an do:

const onInitialize = ({ actions }) => actions.isomorphicOnInitialize()

Now you can call this action manually when on the server 😃

Or just manually call it on the client as well:

const overmind = createOvermind(config)
overmind.actions.isomorphicOnInitialize()

I will write about it in the docs 😃

[suevalov]

Hi @christianalfoni! I’ve stumbled upon with this limitation as well and I don’t see any reasons why the actions should not be available in SSR version.

Basically we should be able to render the application on a server and hydrate all mutations at the end of the render without any limitations.

Something like this: https://github.com/zeit/next.js/tree/canary/examples/with-mobx-state-tree-typescript