[Bug] axisTick中的interval控制刻度线的显隐异常

[FollowTheCause4]

Version

5.3.0

Link to Minimal Reproduction

No response

Steps to Reproduce

在使用interval时，使用true or false 控制刻度线的显隐，实际出现情况与预设情况不同
axisTick: {
length: 50,
interval: index=> {
const checkLst = [true, false, false,true, false, false, false, false]
return checkLst[index]
}
}

Current Behavior

interval：为true，刻度线出现，为false，刻度线不出现

Expected Behavior

true or false 可以直接且正确的控制刻度线的显隐

Environment

- OS:
- Browser:
- Framework:

Any additional comments?

当true的数量较少或者在首位的时候，会出现异常场景

true的未知出现的不正确

[echarts-bot]

@FollowTheCause4 It seems you are not using English, I've helped translate the content automatically. To make your issue understood by more people and get helped, we'd like to suggest using English next time. 🤗

TRANSLATED

TITLE

[Bug] The interval in axisTick controls the hidden anomalies of tick marks

BODY

Version

5.3.0

Link to Minimal Reproduction

No response

Steps to Reproduce

When using interval, use true or false to control the display and hide of tick marks, the actual situation is different from the preset situation
axisTick: {
length: 50,
interval: index=> {
const checkLst = [true, false, false, true, false, false, false, false]
return checkLst[index]
}
}

Current Behavior

interval: true, tick marks appear, false, tick marks do not appear

Expected Behavior

true or false can directly and correctly control the display and hide of the tick marks

Environment

- OS:
- Browser:
- Framework:

Any additional comments?

When the number of true is small or in the first place, there will be abnormal scenarios

true unknown appears incorrect

[github-actions]

This issue has been automatically marked as stale because it did not have recent activity. It will be closed in 7 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this issue.

[github-actions]

This issue has been automatically closed because it did not have recent activity. If this remains to be a problem with the latest version of Apache ECharts, please open a new issue and link this to it. Thanks!