fix(marker): fix markArea doesn't show when using x/y pixel but coord is not defined

[jiawulin001]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

Fix the error that occurs when declaring area with x/y in markArea

Fixed issues

• 使用markarea的x，y出错 #5832
• 柱状图的markArea属性通过x和y设置标记区域报错 #7055
• 在柱状图中设置markArea报错 #10074
• fix [Bug] that cannot be rendered normally when makearea data is the scale field between two screen coordinates #17344

Details

Before: What was the problem?

As is described in issues, when setting x and y to denote an area for markArea, the error occurs. This is caused becasue lt and rb returned by dataTransform() has no attribute coord when user does not specify coord in markArea.data. So when running the following code, Echarts reads lt.coord and throw an error.

echarts/src/component/marker/MarkAreaView.ts

Lines 69 to 79 in 11a9247

	const lt = markerHelper.dataTransform(seriesModel, item[0]);
	const rb = markerHelper.dataTransform(seriesModel, item[1]);
	// FIXME make sure lt is less than rb
	const ltCoord = lt.coord;
	const rbCoord = rb.coord;
	ltCoord[0] = retrieve(ltCoord[0], -Infinity);
	ltCoord[1] = retrieve(ltCoord[1], -Infinity);
	rbCoord[0] = retrieve(rbCoord[0], Infinity);
	rbCoord[1] = retrieve(rbCoord[1], Infinity);

After: How does it behave after the fixing?

Now before dataTransform() return an item, a check is added and make sure there's a coord attribute in it (even coord is not needed). And there will be no errors caused by this.

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#xxx

Misc

ZRender Changes

• 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.

[Ovilia]

LGTM

[echarts-bot]

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