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
Bug 1: using empty string as datum name breaks chart generation ("Uncaught TypeError: box is undefined").
Bug 2: using space character (0x20) as datum name makes legend item almost unclickable:
Using empty name makes little sense, but when using external data it may appear. Currently I'm guarding against it by replacing empty string with non-breaking space (\u00a0).
Hi @piotrp, thanks for the report. But what will be the use case of it?
Every data should have name to be distinguished among multiple data series. Is kinda counter intuitive.
I'm displaying values coming from server logs, e.g. counts of HTTP Referer header. Empty string is not a sane value, but it may appear, and I hit this error when testing various edge cases.
I fully agree that this is not something that should be present in data. My main issue here is that a valid string input breaks chart completely (empty string) or causes degraded user experience (space).
well, in that case to not break, data.idConverter option can be used.
But, unfortunately there's bug(#2808) for now. When the issue is fixed, you can handle empty data name as:
Description
Bug 1: using empty string as datum name breaks chart generation ("Uncaught TypeError: box is undefined").

Bug 2: using space character (0x20) as datum name makes legend item almost unclickable:
Using empty name makes little sense, but when using external data it may appear. Currently I'm guarding against it by replacing empty string with non-breaking space (
\u00a0
).Steps to check or reproduce
JSFiddle: https://jsfiddle.net/tdnp2hfv/
Running:
Results in:
The text was updated successfully, but these errors were encountered: