Nivo: Nivo bar bug introduced in 0.64

[codler]

Describe/explain the bug
The bar crashed in new v0.64, it worked in previous version 0.63.1

To Reproduce
Here is an example, you can switch dependency between versions to see difference.
https://codesandbox.io/s/bar-custom-color-forked-zm065?file=/src/index.js

Expected behavior
It should not crash

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome

[wyze]

Hi @codler, thank you for opening an issue and including a CodeSandbox. The issue is with your data, specifically the last item in the array, it is missing the compareCount key. For now, you can add it with a zero value, but I have a fix incoming.

[codler]

@wyze It is intentionally "missing"/undefined on the last compareCount key, I dont want the bar to show 0 on that item

[wyze]

Okay, no worries, it is something I didn't account for in my refactor.

[stahlmanDesign]

@codler, thank you for creating the CodeSandbox I have this exact same problem. When I generate my data, I only add the data that is pertinent so this failed starting with 0.64.0 for the exact reason you showed in your example.

[stahlmanDesign]

@wyze This is still a bug if you use groupMode: 'stacked' or remove groupMode which defaults to 'stacked'. Here's an example with 0.65.1 where you can see it work with groupMode: 'grouped', and comment it to see it fail https://codesandbox.io/s/bar-custom-color-forked-n7re4?file=/src/index.js

[wyze]

Correct, I opened #1291 to fix it. I tested it out in grouped/stacked, horizontal/vertical, and it matches output of 0.63, before I introduced valueScale prop. I am going to add a couple tests to prevent regression again.