[Bug]: TickDirection isn't working

[andrew20012656]

Describe the bug / 问题描述

I have set my chart config to the following, but the tick isn't changing direction no matter i set tickDirection to "positive" or "negative". I'm wondering if I input anything wrong here.

 const config = {
            xField: "index",
            legend: true,
            children: [
                {
                    data: columnChartDatumList,
                    type: "interval",
                    yField: "value",
                    colorField: "type",
                    stack: true,
                    style: {
                        maxWidth: 80,
                    },
                },
                {
                    data: lineChartDatumList,
                    type: "line",
                    yField: "value",
                    colorField: "name",
                    axis: { y: { position: "right" } },
                },
            ],
            axis: {
                x: {
                    tickFilter: (_: string | number | Date, i: number) => i % 12 == 0,
                    tickDirection: 'negative',
                }
            }
        };

Reproduction link / 复现链接

No response

Steps to Reproduce the Bug or Issue / 重现步骤

No response

Version / 版本

🆕 2.x

OS / 操作系统

• macOS
• Windows
• Linux
• Others / 其他

Browser / 浏览器

• Chrome
• Edge
• Firefox
• Safari (Limited support / 有限支持)
• IE (Nonsupport / 不支持)
• Others / 其他

[dosubot]

Hi @andrew20012656! I'm Dosu and I’m helping the ant-design-charts team.

Your config is correct according to the documentation—tickDirection is listed as a supported axis property and should control the tick orientation source. However, a code search shows that tickDirection is only mentioned in the docs and not actually implemented in the codebase, so it currently has no effect.

If you need to customize tick appearance, you might try other axis tick properties like tickLength, tickStroke, or use a custom tickFormatter for more control. For now, direct tick direction control isn't available—keep an eye on future releases if this feature is important for your use case.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}