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
The objects passed for the prop data in the bar chart have their falsy (undefined, null, 0, etc) keys removed. It is bad because 0 != null, for example. Other reasons for why it is bad can be found in this issue from 2021: #1817, which relates the same problem. Since it was closed due to inactivity and the problem is still happening, I've open this issue again.
Expected behavior
I wish that these value were kept, then we could use them on tooltips and extra layers.
An example for an expected behavior can also be found in the last issue: https://codesandbox.io/s/nivo-playground-forked-8dhxye
Screenshots
From the previous issue:
Desktop (please complete the following information):
OS: Ubuntu 22.04
Browser: chrome
Nivo version: 0.80
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!
Describe/explain the bug
The objects passed for the prop
data
in the bar chart have their falsy (undefined
,null
,0
, etc) keys removed. It is bad because0 != null
, for example. Other reasons for why it is bad can be found in this issue from 2021: #1817, which relates the same problem. Since it was closed due to inactivity and the problem is still happening, I've open this issue again.To Reproduce
The same test case from the old issue: https://codesandbox.io/s/nivo-playground-forked-p3wlo?file=/package.json
Steps to reproduce the behavior:
data
prop from the chart:Expected behavior
I wish that these value were kept, then we could use them on tooltips and extra layers.
An example for an expected behavior can also be found in the last issue: https://codesandbox.io/s/nivo-playground-forked-8dhxye
Screenshots
From the previous issue:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: