You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect that there is a bug somewhere in makeComponent code where it branches on non-null drivers argument, but I haven't done any actual investigation.
The text was updated successfully, but these errors were encountered:
I've stumbled upon many bug reports that mention some kind of xs.combine(xs.of('A'), xs.of('B')) under the hood, so I would recommend checking the blog post and refactoring your application to avoid diamond shapes. At least it seems like it's a xstream glitch, not an issue specific to @cycle/react.
In fact, using xs.combine(xs.of('A'), xs.of('B')) kind of code in my example does work exactly as I intend. It's the other thing that doesn't, and I don't see how glitches can be a problem here.
Full code here: https://codesandbox.io/s/quirky-butterfly-0pdjd?file=/src/index.ts
Given the code above, I get an empty webpage with no components rendered, even though the DOM stream does fire with valid component data.
I can make this work by either removing drivers:
or by replacing my Counter components with something trivial:
I suspect that there is a bug somewhere in
makeComponent
code where it branches on non-nulldrivers
argument, but I haven't done any actual investigation.The text was updated successfully, but these errors were encountered: