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
Describe/explain the bug
When rendering the line graph the data points are not connected in the expected order even though the data set is set up correctly. To Reproduce
I can't find a way to reproduce consistently. Sometimes it happens, and sometimes it does not.
I'm not using the most current version of Nivo since I'm tied to node 14 and using the latest version of Nivo causes dependency issues.
Here are the versions of Nivo I'm using:
"@nivo/core": "^0.79.0",
"@nivo/line": "^0.79.0",
"@nivo/pie": "^0.79.0",
I don't know exact problem, but I faced with the same problem and solved it by disabling animations. From first thought many re-renders in the same time may cause this problem. While the react-spring still has not finished animating, a re-render occurs, which interrupts the initial animation and starts a new one, in some cases the interrupted animation freezes at the random point.
@wastedev, for animations, this is probably due to how the identity of a point is preserved while animating, but I don't have a solution yet for this specific issue.
Describe/explain the bug
When rendering the line graph the data points are not connected in the expected order even though the data set is set up correctly.
To Reproduce
I can't find a way to reproduce consistently. Sometimes it happens, and sometimes it does not.
I'm not using the most current version of Nivo since I'm tied to node 14 and using the latest version of Nivo causes dependency issues.
Here are the versions of Nivo I'm using:
"@nivo/core": "^0.79.0",
"@nivo/line": "^0.79.0",
"@nivo/pie": "^0.79.0",
Here is a code snip of how I'm setting up.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context
It happens with small and large data sets
The text was updated successfully, but these errors were encountered: