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
The chart is rendered correctly with respect to valid values (e.g. the values that are defined in the Y axis data parameter) and "null" (note that null in double quotes as a string) but incorrectly regarding the native JavaScript null value. For instance, in the included example, the last three values are JavaScript native null has been rendered as legit ones with the dots at the value A.
Expected Behavior
The chart should not render any dots regarding the input data null (without double quotes).
Surprisingly, ECharts renders correctly the value "null" (null inside double quotes as a legit JS string, not the native null value).
Another note, ECharts renders correctly if the input data is the native JS undefined value.
Environment
- OS: N/A
- Browser: N/A
- Framework: N/A
Any additional comments?
No response
The text was updated successfully, but these errors were encountered:
Version
5.3.1
Link to Minimal Reproduction
https://codesandbox.io/s/echarts-category-83rl4d?file=/src/index.js
Steps to Reproduce
Current Behavior
The chart is rendered correctly with respect to valid values (e.g. the values that are defined in the Y axis
data
parameter) and"null"
(note thatnull
in double quotes as a string) but incorrectly regarding the native JavaScriptnull
value. For instance, in the included example, the last three values are JavaScript nativenull
has been rendered as legit ones with the dots at the valueA
.Expected Behavior
The chart should not render any dots regarding the input data
null
(without double quotes).Surprisingly, ECharts renders correctly the value
"null"
(null
inside double quotes as a legit JS string, not the nativenull
value).Another note, ECharts renders correctly if the input data is the native JS
undefined
value.Environment
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: