Chris Williams

any update on this or is there a workaround (here or in `neo4j-graphql-js`)? this is a dealbreaker for integration with our current graph, where we have modeled things like `:Org:User`...

I don't think I had this problem in my application using `useRef` with a couple of checks and cleanup. ```tsx function MyComponent() { const cyRef = useRef(); // cleanup cytoscape...

as this is a library we've left polyfilling up to the lib consumers to minimize bundle size. you likely need to `import '@babel/polyfill;'` at the entry point of your app...

Hmm, no idea what that error is. Maybe ditch the `polyfill` and instead just add the runtime since that's the original error. Please follow the instructions in the [babel documentation](https://babeljs.io/docs/en/babel-runtime)....

Sorry, I'm not going to be able to help you without more information and a minimally reproducible example.

Hey @si-harps, thanks for checking out `@data-ui`. This isn't currently supported, but it's a great suggestion! I think it wouldn't be too hard to implement, I think we'd just need...

Hi @NaveenShanmugam, thanks for checking out `@data-ui` 👍 this is not currently supported in the `histogram` package, though it should be relatively to implement similar to how the `xy-chart` [implements...

Hey @wulucxy you're correct that this is _not_ supported yet. This type of chart is very confusing and so far we've purposefully not implemented it. That said, we will probably...

fwiw, my typical suggestion to stakeholders that want this type of chart is to stack two charts on top of each other, with separate y-axes and matched x-axes.

interesting thought, here's a [codesandbox](https://codesandbox.io/s/v1vzolrl93) with a working demo. I think unfortunately you'd have to have one chart render both series, one invisible, and handle the mouse events for **both**...