Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

在多折线图里,如果dimensions里有负数,则其对应的那条折线无法绘制 #10343

Closed
KingJeason opened this issue Apr 23, 2019 · 1 comment · Fixed by #10346, OpenTMI/opentmi-default-gui#32 or DeviaVir/zenbot#2011 · May be fixed by dyna-dot/iClient-JavaScript-s#1
Labels

Comments

@KingJeason
Copy link

Version

4.1.0-rc.1

Reproduction link

https://codepen.io/SonnyW/pen/axaOvy

Steps to reproduce

见链接

What is expected?

负数对应的曲线可绘制

What is actually happening?

没有绘制

@echarts-bot
Copy link

echarts-bot bot commented Apr 23, 2019

Hi! We've received your issue and please be patient to get responded. 🎉
The average response time is expected to be within one day for weekdays.

In the meanwhile, please make sure that you have posted enough image to demo your request. You may also check out the API and chart option to get the answer.

Have a nice day! 🍵

@echarts-bot echarts-bot bot added bug pending We are not sure about whether this is a bug/new feature. waiting-for-help labels Apr 23, 2019
susiwen8 added a commit to susiwen8/echarts that referenced this issue Apr 23, 2019
@Ovilia Ovilia removed pending We are not sure about whether this is a bug/new feature. waiting-for-help labels May 5, 2019
100pah added a commit that referenced this issue May 5, 2019
Fix negetive number or string exist in dimensions array, the correspo…
100pah added a commit that referenced this issue May 12, 2019
* 'master' of https://github.com/apache/incubator-echarts:
  Update langEN.js
  Improve based on revision
  Fix grammar
  Add aria defaults for lang-en
  Tweak the "is string" check.
  Check if dataDims[0] type is number or not
  Fix negetive number or string exist in dimensions array, the corresponding line won't show (#10343)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment