render being called twice about om

[swannodette]

pending state is indeed merged in after will-mount. Do you have minimal example where you aren't seeing this? Thanks.

[colinkahn]

Of course. Here's a gist with a simple app based mostly on what you had done in the todo app.

https://gist.github.com/colinkahn/8338003

You can see that the app-state has :projects, and there's one default project populated in there. This project ends up being created on the first render pass, but at that point render shows comm as nil. This results in an the error Uncaught Error: No protocol method WritePort.put! defined for type null: when you try to delete the default project. Then render gets triggered again, gets comm from owner, so projects created later are fine and can be deleted as expected.

Logging out everything will-mount is called first, then the first render, but w/ comm nil, then render is called again with comm being the async channel.

[swannodette]

Thanks for the minimal example, will look into it.

[swannodette]

I cannot replicate this using master. I see a value printed out on both renders, what version of Om are you using? Render being called twice is not a very serious issue, we can optimize this at some point in the future.

[colinkahn]

Looks like this was due to me not using the latest version of ClojureScript, sorry about that. Thanks for looking into it anyways.