fix(Ellipsis): Correction of text（纠正错别字）

[kid-kang]

🤔 这个变动的性质是？

• 新特性提交
• 日常 bug 修复
• 站点、文档改进
• 演示代码改进
• 组件样式/交互改进
• TypeScript 定义更新
• 包体积优化
• 性能优化
• 功能增强
• 国际化改进
• 重构
• 代码风格优化
• 测试用例
• 分支合并
• 其他改动（是关于什么的改动？）

🔗 相关 Issue

💡 需求背景和解决方案

纠正错别字：文本点击是触发 -> 文本点击时触发

☑️ 请求合并前的自查清单

⚠️ 请自检并全部勾选全部选项。⚠️

• 文档已补充或无须补充
• 代码演示已提供或无须提供
• TypeScript 定义已补充或无须补充
• fork仓库代码是否为最新避免文件冲突
• Files changed 没有 package.json lock 等无关文件

Summary by CodeRabbit

• 新功能

  • 更新了Ellipsis组件的onClick属性描述，增强了事件触发的清晰度。

• 文档

  • 更新了Ellipsis组件的文档，修正了onClick属性的描述，确保信息准确性和一致性。

[coderabbitai]

Walkthrough

此次更改主要集中在 scripts/properties.json 文件及 Ellipsis 组件的文档更新。对 onClick 属性的描述进行了修改，以增强其清晰度。其他组件的属性保持不变，文档结构一致，确保功能正常。整体上，更新旨在提高组件属性的文档质量，而不影响底层功能。

Changes

文件路径	更改摘要
scripts/properties.json	更新 Ellipsis 组件的 onClick 属性描述：从 "文本点击是触发" 修改为 "文本点击时触发"。
src/packages/ellipsis/doc.md	更新 Ellipsis 组件的 onClick 属性描述：从 "文本点击是触发" 修改为 "文本点击时触发"。
src/packages/ellipsis/doc.taro.md	更新 Ellipsis 组件的 onClick 属性描述：从 "文本点击是触发" 修改为 "文本点击时触发"。

Possibly related PRs

• chore: fix typos #2300: 此PR涉及修复文档中的拼写错误，包括 Ellipsis 组件的 onClick 属性描述，与本PR中的更改直接相关。

Suggested labels

2.x

Suggested reviewers

• oasis-cloud

Poem

在兔子洞里有新变化，
onClick 描述更清晰，
文档更新如春风，
让我们欢呼，乐无穷！
兔子跳跃，心花怒放，
这份更新真是棒！ 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between aeabe98 and 17edca4.

📒 Files selected for processing (3)

• scripts/properties.json (1 hunks)
• src/packages/ellipsis/doc.md (1 hunks)
• src/packages/ellipsis/doc.taro.md (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• scripts/properties.json
• src/packages/ellipsis/doc.md
• src/packages/ellipsis/doc.taro.md

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.98%. Comparing base (aeabe98) to head (17edca4).
Report is 1 commits behind head on V3.0.

Additional details and impacted files

@@           Coverage Diff           @@
##             V3.0    #2778   +/-   ##
=======================================
  Coverage   83.98%   83.98%           
=======================================
  Files         220      220           
  Lines       17876    17876           
  Branches     2676     2676           
=======================================
  Hits        15013    15013           
  Misses       2858     2858           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles