feat(custom): support compoundPath in custom series renderItem

[Ovilia]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

This PR supports compoundPath in custom series renderItem. It can be used as:

renderItem(params, api) {
    return {
        type: 'compoundPath',
        shape: {
            paths: [rect, circle, ...]
        }
    }
}

Fixed issues

Details

Before: What was the problem?

compondPath is not supported so that we cannot make complex objects that looks like the union of shapes. If such shapes have opacity and intersection, it's hard to implement without a compoundPath.

After: How does it behave after the fixing?

compondPath is supported.

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@3d71262

Misc

ZRender Changes

• This PR depends on ZRender changes (fix(path): using appendData instead of setData for path ecomfe/zrender#1096).

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.

This PR depends on ZRender changes. Please update the ZRender dependency to the latest nightly version including this change, which takes place everyday at 8:00 UTC (16:00 Beijing Time).
You can use npm i zrender@npm:zrender-nightly@dev to update package.json.
If you have any question about this, please leave a comment and we will give you extra help on this.

[github-actions]

The changes brought by this PR can be previewed at: https://echarts.apache.org/examples/editor?version=PR-20402@9fb4073

[echarts-bot]

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

[100pah]

I think probably we should not public that buildPath.

1. That function is not officially public in any other place, including not public in custom series path.
2. If publish buildPath function, the signature must not be changed or need backward compat when changing. And the parameter of buildPath includes ctx, which is PathProxy or CanvasContext. Although they are always accessible never be officially public and promised in API stability.

Is it needed in some scenarios? @Ovilia