Closed corps closed 8 years ago
I'll look into it later today.
Sorry it took me a long time to look back at this issue. Though I wasn't able to reproduce this issue for 2.0. It should be now fixed in 3.0 since I've changed the inner render method by using cloneElement
. If you still have this error in 3.0, feel free to reopen this issue.
Hey there,
First off wanted to say I'm a fan of cycle-react and have been using it without issue for awhile now.
Recently, however, I moved towards performing a server side render of a page using a cycle react component at the top level and have had problems.
This unfortunately throws this error:
But here's the strange thing -- by merely wrapping the cycle react component in an outer element, not only does the error goes away but the component successfully renders.
The above code works as expected. Weird.