feat(bar): add startValue option to specify where the bars start

[jiawulin001]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

barSeries.startValue is added for users to specify where the bars start.

Fixed issues

• fix 柱状图是否支持从最小值开始画，现在柱状图都只能从0开始画 #15463
• fix [Bug] When polar coordinates are negative, it still renders the bar from 0. #16840
• fix [Bug]the bar chart starts at 0, and setting xAxis.axisline.onZero: false won't make it start at the minimum #17077

Details

Before: What was the problem?

As stated in the issues. Users cannot specify the start value of bars.

issue #16840	issue #17077

After: How is it fixed in this PR?

Users now can specify barSeries.startValue to set the starting value of bars. Stack and multi-axes are also tested to be running correctly.

issue #16840 (startValue = -200)	issue #17077 (startValue = -150)

Document Info

One of the following should be checked.

• This PR doesn't relate to document changes
• The document should be updated later
• The document changes have been made in apache/echarts-doc@670e4a2

Misc

ZRender Changes

• This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

bar-startValue.html

Others

Merging options

• Please squash the commits into a single one when merging.

Other information

[echarts-bot]

Thanks for your contribution!
The community will review it ASAP. In the meanwhile, please checkout the coding standard and Wiki about How to make a pull request.

Document changes are required in this PR. Please also make a PR to apache/echarts-doc for document changes and update the issue id in the PR description. When the doc PR is merged, the maintainers will remove the PR: awaiting doc label.

[susiwen8]

• This might fix 柱状图是否支持从最小值开始画，现在柱状图都只能从0开始画 #15463 Could you add it in PR descrption

[jiawulin001]

Sure, it's done.

[Ovilia]

This looks to be a useful feature, only that more test cases are required. For example, to test the cases when min or max values are defined for the axis, or when r does start from 0 for polar bars.

And you need to run the visual tests to test the differences caused by this PR.

npm run test:visual

Choose the latest nightly build to compare with the one build from your source code.

[jiawulin001]

@Ovilia Extra testcases are added and all visual tests are passed.

[Ovilia]

It seems there are a lot of commits that are already in the master branch. Try this solution.

[Ovilia]

Please also add a startValue test with dataZoom component.

[jiawulin001]

@olivia Good intuition on dataZoom! I tested and found startValue not compatible with dataZoom.
I've revised the code and now it works well with dataZoom and more naturally incorporate in original code. Also min/max set by user now has higher priority over startValue. Another change is that startValue is moved under axis rather than series, which I think is more reasonable.
Relevant test cases concerning dataZoom, priority and polar are all added. Please check them out.

[dailijian]

@jiawulin001 Merging is blocked，

[echarts-bot]

To reviewers: If this PR is going to be described in the changelog in the future release, please make sure this PR has one of the following labels: PR: doc ready, PR: awaiting doc, PR: doc unchanged

This message is shown because the PR description doesn't contain the document related template.

[echarts-bot]

Congratulations! Your PR has been merged. Thanks for your contribution! 👍

[plainheart]

This option is unused here and should be removed in the next version.