[Feature] [axis] add alignTicks for mutliple axis alignment.

[pissang]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

This PR adds alignTicks option to allow ticks alignment between multiple value or log axis.

Similar PR: #13210

How it Works

When a value/log axis is set to alignTicks: true. It will find the first value/log axis on the same dimension that is not use alignTicks and align the ticks to it.

The align algorithm is bacially from radar series, which already has ticks alignment between multiple indicator axes, with some enhancement on the corner cases. The simple idea is find a good interval that having minimal extent that can contain the data. Here is a detail explaination

1. Get the ticks number of axis align to. The splitNumber is ticksNumber - 1
2. Calculate extent and interval with this splitNumber using calcNiceExtent.
3. The calculated ticks number is not excatly same to the target number. So we need an extra refine step, the refine step will consider four cases:
   • If min and max are both fixed. It will simply calculate the interval by (max - min) / splitNumber
   • If max is fixed. Try to calculate min by max - interval * splitNumber. interval is from the second step. If the calculated min is larger than the minimal value. Increase interval util min is less than the minimal value.
   • If min is fixed. Similar to max fixed case.
   • If both min and max are not fixed. Set max to extent[1] calculated from the second step. Then it's similar to the max fixed case. Note if the calculated min and max cross the zero value. We need to check if the data extent cross and make sure they are both positive or negative.
4. If the axis align to has set min or max. We need to adjust the calculated min and max proportionally.

Limitations

1. Time axis is not supported yet because the ticks calculation has becoming really complex since 5.0
2. Using alignTicks with complex min, max value, e.g. 'dataMin', 'dataMax', will lead to unreadable ticks.

Fixed issues

#11390
#10928

Details

Before: What was the problem?

After: How is it fixed in this PR?

More conformance tests

Misc

• The API has been changed (apache/echarts-doc#xxx).
• This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

N.A.

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.

The pull request is marked to be PR: author is committer because you are a committer of this project.

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.

[Ovilia]

LGTM

[echarts-bot]

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

[maxdor1]

Hi

I can't build an online example because my data is sensitive but here is a screenshot showing that the last right axis min is not calculated correctly:

Min value of this dataset is 58.854 but the min axis tick shows as 58.86