fix(overlay): 扩大点击范围

[oasis-cloud]

Summary by CodeRabbit

• 重构
  • 调整了多个示例组件的交互逻辑，将点击响应从内部显示区域转移到更直观的外部交互区域，使点击操作更加一致和易用。

[coderabbitai]

Walkthrough

此次变更对多个 Taro 示例组件的点击事件处理逻辑进行了调整。在各个 demo 组件中，原先由内部 View 组件处理点击事件的逻辑被迁移到外层的 Cell 组件。点击操作现在直接由 Cell 组件触发，从而调用触发状态更新的方法。公开或导出的实体声明未发生改动。

Changes

文件路径	变更描述
src/packages/overlay/demos/taro/demo1.tsx src/packages/overlay/demos/taro/demo2.tsx src/packages/overlay/demos/taro/demo3.tsx src/packages/overlay/demos/taro/demo4.tsx src/packages/overlay/demos/taro/demo5.tsx src/packages/overlay/demos/taro/demo6.tsx	将 onClick 事件处理从 View 组件迁移到 Cell 组件中，各 demo 中通过调整交互层级实现了同一操作触发对应状态更新。

Sequence Diagram(s)

sequenceDiagram
    participant 用户 as User
    participant Cell as Cell组件
    participant Demo as Demo组件
    participant View as View组件

    用户->>Cell: 单击 Cell
    Cell->>Demo: 调用 handleToggleShow()
    Demo->>View: 根据状态更新视图

Loading

Possibly related PRs

• fix(hoverbutton): 恢复icon,简化demo #2725：此 PR 也针对 demo 组件的事件处理结构进行了变更，均涉及将点击事件从 View 移至 Cell，存在较强的代码层面关联性。

Suggested reviewers

• irisSong
• Alex-huxiyang

Poem

我是一只跳跃的兔子，
代码森林里乐无穷，
点击穿过层层视图，
交互流转意缤纷，
祝改动顺畅又精彩 🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9a903a0 and 2bdebea.

📒 Files selected for processing (6)

• src/packages/overlay/demos/taro/demo1.tsx (1 hunks)
• src/packages/overlay/demos/taro/demo2.tsx (1 hunks)
• src/packages/overlay/demos/taro/demo3.tsx (1 hunks)
• src/packages/overlay/demos/taro/demo4.tsx (1 hunks)
• src/packages/overlay/demos/taro/demo5.tsx (1 hunks)
• src/packages/overlay/demos/taro/demo6.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test

🔇 Additional comments (6)

src/packages/overlay/demos/taro/demo5.tsx (1)

17-18: 优化了用户交互体验

将点击事件从内部的 View 组件移至外部的 Cell 组件，这样扩大了可点击区域，提高了用户的交互体验。用户现在可以点击整个 Cell 区域来触发遮罩层的显示，而不仅限于文本内容区域。

src/packages/overlay/demos/taro/demo2.tsx (1)

15-16: 点击区域扩展优化

将点击事件处理从 View 组件移至 Cell 组件是一个很好的改进。这样扩大了可点击区域，使用户在点击时不必精确点击文本部分，整个 Cell 区域都可响应点击事件，提高了组件的可用性。

src/packages/overlay/demos/taro/demo4.tsx (1)

15-16: 交互区域优化

这一修改与其他 Demo 组件保持一致，将点击事件从 View 组件移至 Cell 组件，扩大了可交互区域。这种模式变更提高了组件的易用性，是一个很好的用户体验改进。

src/packages/overlay/demos/taro/demo1.tsx (1)

15-16: 用户体验改进

将点击事件从 View 移至外层 Cell 组件是一个很好的改进。这样做扩大了可点击区域，使组件更加易用，尤其是在移动设备上操作时。这种统一的交互模式也使所有 Demo 组件保持了一致的用户体验。

src/packages/overlay/demos/taro/demo6.tsx (1)

33-34: 良好的可用性改进！

将点击事件处理从内部的 View 组件移到外层的 Cell 组件是一个很好的改进。这样扩大了可点击区域，使用户可以点击整个 Cell 而不仅限于文本区域来触发遮罩显示，提高了组件的可用性和用户体验。

src/packages/overlay/demos/taro/demo3.tsx (1)

15-16: 点击区域扩展的优化！

将 onClick 事件处理从 View 移至 Cell 组件是一个很好的改进。这样做扩大了可点击的区域，使用户可以点击整个 Cell 而不只是文本内容来触发遮罩显示。这种模式的统一应用提高了组件库的一致性和用户体验。

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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 generate docstrings to generate docstrings for this 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 86.95%. Comparing base (9a903a0) to head (2bdebea).
Report is 7 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #3117   +/-   ##
==========================================
  Coverage      86.95%   86.95%           
==========================================
  Files            280      280           
  Lines          18456    18456           
  Branches        2786     2786           
==========================================
  Hits           16049    16049           
  Misses          2402     2402           
  Partials           5        5           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[xiaoyatong]

看下两个端，这次让两端保持一致好了~