baobab-react with react-router >=1.0

rooting-our-top-level-componen describes how to root a top level component.

ReactDom.render(
    require('baobab-react/higher-order').root(tree, App), 
    elem
)

With react-router >= 1.0, top level components are rendered however similar to this

ReactDom.render(
    <Router history={appHistory}>...</Router>,
    elem
)

What is the suggested pattern to use react-baobab with react-router >=1.0?

Applying the mixin pattern (mixins.root and mixins.branch) for rooting the baobab doesn’t seem to work with react-router >=1.0 either.

[Yomguithereal]

The current signature of the root function is root(tree, Component (code here). So it seems that the tree you provide is not a baobab tree. One thing you can also check is if you have the Baobab dep more than once in your deps because if the one used by the higher order function is not the same as the one from which you got your tree, it might cause issues.

[Yomguithereal]

I am happy it worked @hansman. It makes me think I should rollback to identity checking rather than checking the class instance in my tests for a Baobab tree. This would avoid this kind of problems.