fix(slider): Fix trackContainer spelling error.

[songyipan]

Corrected to to fix a spelling error and maintain code consistency. The interface definitions and implementation code in both the Chinese and English documentation have been updated accordingly.

First of all, thank you for your contribution! :-)

Please makes sure that these checkboxes are checked before submitting your PR, thank you!

• Make sure that you follow antd's code convention.
• Run npm run lint and fix those errors before submitting in order to keep consistent code style.
• Rebase before creating a PR to keep commit history clear.
• Add some descriptions and refer relative issues for you PR.

Extra checklist:

if isBugFix :

• Make sure that you add at least one unit test for the bug which you had fixed.

elif isNewFeature :

• Update API docs for the component.
• Update/Add demo to demonstrate new feature.
• Update TypeScript definition for the component.
• Add unit tests for the feature.

Summary by CodeRabbit

修复

• Bug 修复
  • 修正滑块组件样式属性的拼写错误，确保属性命名的准确性和一致性。

[coderabbitai]

📝 Walkthrough

总体说明

该改动修复了滑块组件中的属性名称拼写错误，将 trackContianer 更正为 trackContainer。更改涉及文档文件和源代码，仅涉及属性名称调整，无行为逻辑变化。

变更明细

组织/文件	变更摘要
文档更新 components/slider/index.en-US.md，components/slider/index.zh-CN.md	在 SliderStyle 接口中，属性名称 trackContianer 更正为 trackContainer
实现和样式文件 components/slider/slider.tsx，components/slider/style/index.tsx	修复样式属性名称拼写，在渲染路径和样式定义中统一使用 trackContainer

代码审查工作量估计

🎯 1 (微不足道) | ⏱️ ~3 分钟

• 该改动是重复性、一致的拼写错误修复
• 所有文件中的变更模式相同
• 无需审查复杂的逻辑或控制流

诗

🐰 一只兔子穿过代码的森林，
发现了藏匿已久的打字错误，
trackContianer 变成 trackContainer，
拼写不再模糊，意图更加清晰，
小改动，大精确！✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	PR标题准确反映了主要改动：修复slider组件中trackContainer的拼写错误。标题简洁、清晰，与changeset相关联的所有文件改动（文档、样式、实现代码）都围绕这个拼写修正进行。
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @songyipan, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a minor but important code quality improvement by fixing a spelling error. The change standardizes the trackContainer property name, enhancing readability and maintainability across the Slider component's interface definitions, implementation logic, and both English and Chinese documentation. This ensures all references to the track container are consistent and correctly spelled.

Highlights

• Spelling Correction: Corrected the spelling of trackContianer to trackContainer across the codebase.
• Code Consistency: Ensured consistent naming for the trackContainer property in interface definitions, component implementation, and documentation.
• Documentation Updates: Updated both English (index.en-US.md) and Chinese (index.zh-CN.md) documentation files to reflect the correct spelling.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes a spelling error, changing trackContianer to trackContainer. The correction has been applied consistently across the component implementation, style definitions, and documentation. The addition of newlines at the end of the markdown files is also a good change that aligns with common best practices. The changes are straightforward and well-executed.

[songyipan]

@coderabbitai generate docstrings

[coderabbitai]

✅ Actions performed

Initiated docstring generation; will generate only if new commits exist.

[coderabbitai]

Note

Docstrings generation - SUCCESS
Generated docstrings for this pull request at #1459

[songyipan]

@1uokun 麻烦您有空了看一下我提交的pr，非常感谢
Could you please take a look at the pr I submitted when you have time? Thank you very much