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
Whenever rendering multiple graphs and using minimaps for each one of them, the minimaps gets "lost", specially if passing options props to it because that would trigger the useEffect inside the component to render which destroys and re-renders the minimap, and what that causes is that both minimaps are rendered together instead of each minimap being "inside" its own graph.
This is a very small example of what I'm talking about because I couldn't reproduce everything but you can get the sense of it from that code pen.
Expected behavior
Each minimap would be "attached" to its own graph
Screenshots or Videos
Expected Behavior, happens before I update the component props, as including another view.
Bug after updating props to include another view.
Platform
OS: [Linux]
Browser: [Chrome, Edge]
Additional context
It happens after a component update props but since I can render from 1 to 4 charts in the same component, this should happen and the minimap should still recognize its parent graph and stick to it.
I'm not sure yet how to handle / solve this so I'd appreciate any help here, thanks in advance!!
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever rendering multiple graphs and using minimaps for each one of them, the minimaps gets "lost", specially if passing options props to it because that would trigger the useEffect inside the component to render which destroys and re-renders the minimap, and what that causes is that both minimaps are rendered together instead of each minimap being "inside" its own graph.
Your Example Website or App
https://codesandbox.io/s/funny-montalcini-v89qno?file=/App.tsx
Steps to Reproduce the Bug or Issue
This is a very small example of what I'm talking about because I couldn't reproduce everything but you can get the sense of it from that code pen.
Expected behavior
Each minimap would be "attached" to its own graph
Screenshots or Videos
Expected Behavior, happens before I update the component props, as including another view.
Bug after updating props to include another view.
Platform
Additional context
It happens after a component update props but since I can render from 1 to 4 charts in the same component, this should happen and the minimap should still recognize its parent graph and stick to it.
I'm not sure yet how to handle / solve this so I'd appreciate any help here, thanks in advance!!
The text was updated successfully, but these errors were encountered: