fix: popup 鸿蒙适配弹出时退出app的问题

[xiaoyatong]

🤔 这个变动的性质是？

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

🔗 相关 Issue

💡 需求背景和解决方案

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

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

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

Summary by CodeRabbit

• 重构

  • 优化了弹窗组件的显示逻辑，确保在使用遮罩时内容正确组合和展示。

• Bug 修复

  • 解决了在启用遮罩时可能导致弹窗内容重复渲染的问题，提升了整体稳定性。

[coderabbitai]

Walkthrough

该PR修改了 Popup 组件中的 renderNode 函数，对 overlay 属性的检查方式进行了调整。当 overlay 为 true 时，通过 Overlay 组件包装后调用 renderPop 函数；当 overlay 为 false 时，则直接调用 renderPop。这种改动避免了在 overlay 为 true 时重复渲染 renderPop 的情况，使渲染逻辑更加清晰。

Changes

文件路径	更改摘要
src/.../popup.taro.tsx	修改了 renderNode 函数逻辑，根据 overlay 属性决定是否通过 Overlay 组件调用 renderPop。

Sequence Diagram(s)

sequenceDiagram
    participant Popup组件 as Popup组件
    participant Overlay as Overlay组件
    participant renderPop函数 as renderPop

    Popup组件->>Popup组件: 检查 overlay 属性
    alt overlay 为 true
        Popup组件->>Overlay: 调用 Overlay 组件
        Overlay->>renderPop函数: 执行 renderPop
    else overlay 为 false
        Popup组件->>renderPop函数: 直接执行 renderPop
    end

Loading

Possibly related PRs

• refactor: popup 优化代码 #2944: 与当前PR类似，修改了 Popup 组件中的渲染逻辑和事件处理行为，存在直接的代码层关联。

Suggested reviewers

• oasis-cloud

Poem

我是小兔跳跃间，
代码中亦见晴天，
Overlay 或直接传，
renderPop 从不慌乱，
改变逻辑静待成，全场皆欢喜 🐇🌟
小兔祝你成功连连！

---

📜 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 3080c9c and 4fb23a9.

📒 Files selected for processing (1)

• src/packages/popup/popup.taro.tsx (2 hunks)

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

• GitHub Check: test

✨ Finishing Touches

• 📝 Generate Docstrings

---

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 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 85.97%. Comparing base (3080c9c) to head (4fb23a9).
Report is 1 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #3033   +/-   ##
==========================================
  Coverage      85.97%   85.97%           
==========================================
  Files            281      281           
  Lines          18251    18251           
  Branches        2746     2746           
==========================================
  Hits           15691    15691           
  Misses          2555     2555           
  Partials           5        5           

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