fix(axis):null value item on category axis should be able to show tooltip

[Justin-ZS]

Brief Information

This pull request is in the type of:

• bug fixing
• new feature
• others

What does this PR do?

If the chart uses dataset/axis.encode, the null value items on category axis cannot trigger axis tooltip.(NG)
Try demo

echarts/src/scale/Ordinal.ts

Lines 143 to 147 in b5c4a66

	contain(rank: OrdinalRawValue | OrdinalNumber): boolean {
	rank = this.parse(rank);
	return scaleHelper.contain(rank, this._extent)
	&& this._ordinalMeta.categories[rank] != null;
	}

This check will ignore null value items on category axis, although null is a valid value.

But if the chart uses axis.data, the null value items on category axis can trigger axis tooltip.
In this case, the axis.data will be parsed by getName -- null becomes "null".

echarts/src/data/OrdinalMeta.ts

Lines 50 to 61 in b5c4a66

	static createByAxisModel(axisModel: Model): OrdinalMeta {
	const option = axisModel.option;
	const data = option.data;
	const categories = data && map(data, getName);
	return new OrdinalMeta({
	categories: categories,
	needCollect: !categories,
	// deduplication is default in axis.
	deduplication: option.dedplication !== false
	});
	};

Fixed issues

#20774

Details

Before: What was the problem?

After: How does it behave after the fixing?

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.

[Justin-ZS]

@100pah @Ovilia
Could you help to review the PR? Thanks!

[Ovilia]

@Justin-ZS Thanks for the contribution and sorry for the late reply. I'll review it now. 😄

[github-actions]

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

[Ovilia]

When category value is null or undefined when not using dataset, it's considered as a string 'null' and 'undefined' so I think maybe it's best to align this behavior to this?

option = {
  xAxis: {
    type: 'category',
    data: ['Mon', null, undefined, 'Thu', 'Fri', 'Sat', 'Sun']
  },
  yAxis: {
    type: 'value'
  },
  series: [
    {
      data: [150, 230, 224, 218, 135, 147, 260],
      type: 'line'
    }
  ]
};

The result of this PR is an empty string as category value now.

[Justin-ZS]

When category value is null or undefined when not using dataset, it's considered as a string 'null' and 'undefined' so I think maybe it's best to align this behavior to this?

option = {
  xAxis: {
    type: 'category',
    data: ['Mon', null, undefined, 'Thu', 'Fri', 'Sat', 'Sun']
  },
  yAxis: {
    type: 'value'
  },
  series: [
    {
      data: [150, 230, 224, 218, 135, 147, 260],
      type: 'line'
    }
  ]
};

The result of this PR is an empty string as category value now.

I actually prefer the current behavior of dataset/encode where null/undefined values are rendered as empty strings.
null/undefined are JavaScript keywords that represent empty or missing values, an empty string is more intuitive in most contexts.

Changing it could lead to unexpected issues when users upgrade to a new version.
They would need to implement additional logic to hide null/undefined values or consider i18n.

[Ovilia]

Thanks for your feedback. @plainheart @100pah What do you think about this?