chore: compatible with legacy

[zombieJ]

follow up #522

Summary by CodeRabbit

• 新功能

  • 优化了弹窗显示状态的回调接口，引入更直观的回调方法，同时废弃了旧的方式，提供更一致的用户体验。

• 测试

  • 更新了相关测试用例，确保新接口在控制与非控制场景下均能正确触发弹窗状态变化。

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

此次变更主要针对 trigger 组件回调函数和接口定义进行了调整。在 src/index.tsx 中，TriggerProps 接口新增了 afterOpenChange 属性，用以处理弹窗状态变化，同时将 onPopupVisibleChange 与 afterPopupVisibleChange 标记为弃用。在 generateTrigger 函数内，新旧回调各自按需调用。在 tests/basic.test.jsx 中，相应更新了测试用例，检测新名称的回调逻辑以及新增 mock 函数的调用。

Changes

文件	修改摘要
src/index.tsx	在 TriggerProps 接口中新增 afterOpenChange 属性；将 onPopupVisibleChange 与 afterPopupVisibleChange 标记为弃用；在 generateTrigger 中调用对应回调。
tests/basic.test.jsx	更新测试用例：将 afterPopupVisibleChange 替换为 afterOpenChange，并新增 onPopupVisibleChange 的使用；利用 mock 函数验证弹窗状态变更。

Sequence Diagram(s)

sequenceDiagram
    participant User as 用户
    participant Trigger as Trigger组件
    participant Deprecated as onPopupVisibleChange (弃用)
    participant New as afterOpenChange

    User->>Trigger: 触发弹窗状态变化
    Trigger->>Deprecated: 调用 onPopupVisibleChange（若存在）
    Trigger->>New: 调用 afterOpenChange，传入当前状态

Loading

Possibly related PRs

• Revert "fix: click on shadowDOM popup should not close it" #485: 涉及 generateTrigger 函数和弹窗可见性处理逻辑的修改，与本次变更有直接关联。
• fix: try to fix createPortal close case #492: 测试用例中关于回调命名和弹窗状态处理的更新，与当前改动存在相似改进。
• refactor: rename internal api #522: 重点在接口中回调名称的重命名，与此次 TriggerProps 接口的调整紧密相关。

Poem

我是一只跳跃的小兔子，
代码花园里乐趣无穷，
新增回调迎风摇曳，
弃旧迎新正当时，
每一次变更都欢喜，
🐰 让我与代码共舞不停！

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/index.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-react".

(The package "eslint-plugin-react" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react@latest --save-dev

The plugin "eslint-plugin-react" was referenced from the config file in ".eslintrc.js » /node_modules/.pnpm/@umijs[email protected][email protected]/node_modules/@umijs/fabric/dist/eslint.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

tests/basic.test.jsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-react".

(The package "eslint-plugin-react" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react@latest --save-dev

The plugin "eslint-plugin-react" was referenced from the config file in ".eslintrc.js » /node_modules/.pnpm/@umijs[email protected][email protected]/node_modules/@umijs/fabric/dist/eslint.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

---

📜 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 9601b4a and 252a8e8.

📒 Files selected for processing (2)

• src/index.tsx (4 hunks)
• tests/basic.test.jsx (4 hunks)

✨ 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 plan to trigger planning for file edits and PR creation.
• @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 97.72%. Comparing base (9601b4a) to head (252a8e8).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #523   +/-   ##
=======================================
  Coverage   97.71%   97.72%           
=======================================
  Files          13       13           
  Lines         788      790    +2     
  Branches      231      231           
=======================================
+ Hits          770      772    +2     
  Misses         18       18           

☔ 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.