refactor: useId of rc-util

[zombieJ]

Summary by CodeRabbit

• 杂项
  • 更新了依赖包 "@rc-component/select" 的版本至 "~1.0.7"。

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cascader	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 3, 2025 1:38pm

[coderabbitai]

Walkthrough

本次变更将依赖包 @rc-component/select 的版本从 ~1.0.0 升级到 ~1.0.7，并将 src/Cascader.tsx 文件中 useId 的导入路径由 @rc-component/select 切换为 @rc-component/util，无其他逻辑调整。

Changes

文件/分组	变更摘要
package.json	更新 @rc-component/select 依赖版本至 ~1.0.7
src/Cascader.tsx	useId 的导入路径由 @rc-component/select 改为 @rc-component/util

Poem

小兔挥爪轻轻点，
依赖升级更稳健。
useId 跳新家，
组件协作更无瑕。
代码清爽如新草，
快乐开发每一秒！
🐇✨

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/Cascader.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "prettier" to extend from. Please check that the name of the config is correct.

The config "prettier" was referenced from the config file in "/.eslintrc.js".

If you still have problems, 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 3aaa70c and e1b23d3.

⛔ Files ignored due to path filters (1)

• tests/__snapshots__/search.spec.tsx.snap is excluded by !**/*.snap

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/Cascader.tsx (1 hunks)

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

• GitHub Check: test / react component workflow

🔇 Additional comments (2)

package.json (1)

46-46:

❓ Verification inconclusive

升级 @rc-component/select 依赖版本
本次将 @rc-component/select 从 ~1.0.0 更新到 ~1.0.7，请确认新版本是否包含破坏性变更或 API 调整，避免影响现有功能。建议查看官方 CHANGELOG 或执行以下命令验证：

---

🏁 Script executed:

npm view @rc-component/select@~1.0.7 changelog

Length of output: 48

---

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

# 获取仓库地址
repo_url=$(npm view @rc-component/[email protected] repository.url)
echo "Repository URL: $repo_url"

# 提取 owner/repo
repo_path=$(echo "$repo_url" | sed -E 's#.*github.com[:/]+([^/]+/[^/]+)(\.git)?#\1#')
echo "Repository Path: $repo_path"

# 尝试获取 CHANGELOG.md
echo -e "\n--- CHANGELOG.md (前 50 行) ---"
curl -sL https://raw.githubusercontent.com/$repo_path/v1.0.7/CHANGELOG.md | sed -n '1,50p' || echo "未找到 CHANGELOG.md"

# 尝试获取 HISTORY.md
echo -e "\n--- HISTORY.md (前 50 行) ---"
curl -sL https://raw.githubusercontent.com/$repo_path/v1.0.7/HISTORY.md | sed -n '1,50p' || echo "未找到 HISTORY.md"

Length of output: 921

---

请手动核查 @rc-component/select@~1.0.7 更新是否存在破坏性变更

在官方仓库中未找到 CHANGELOG.md 或 HISTORY.md，也无法通过 npm view … changelog 自动获取更新日志。

请开发者执行以下操作，以避免潜在的兼容性风险：

• 前往 https://github.com/react-component/select 仓库，对比 v1.0.0 与 v1.0.7 之间的提交（或标签）差异
• 重点验证筛选组件的核心 API 和样式渲染是否有变更
• 在项目中运行关键用例，确保升级后功能正常

文件位置：

• package.json 第 46 行："@rc-component/select": "~1.0.7",

src/Cascader.tsx (1)

9-9:

❓ Verification inconclusive

调整 useId 导入来源
已将 useId 从 @rc-component/select/lib/hooks/useId 迁移到 @rc-component/util/lib/hooks/useId，请确认在 @rc-component/util@^1.2.1 包中该路径下确实导出了 useId 且接口与原有版本保持一致。建议运行以下命令快速验证：

---

🏁 Script executed:

rg "export default" -A2 "node_modules/@rc-component/util/lib/hooks/useId"

Length of output: 161

---

为进一步确认 useId 在 @rc-component/util 包中的实际位置及导出情况，请运行以下脚本：

此脚本将帮助确认文件路径与导出定义。如仍未找到，请手动检查包版本或与维护者确认接口是否已迁移或重命名。

---

🏁 Script executed:

#!/usr/bin/env bash
set -e

echo "1. 列出 hooks 目录下所有文件，查找 useId 相关文件："
find node_modules/@rc-component/util/lib/hooks -type f | grep -i useid || echo "未在该目录找到 useId 相关文件"

echo -e "\n2. 在整个 util 包中搜索 useId 的导出声明："
rg "export.*useId" -R node_modules/@rc-component/util || echo "未在 util 包中检索到 useId 导出"

Length of output: 875

---

请运行以下脚本，进一步定位 useId 文件及其导出声明：

---

🏁 Script executed:

#!/usr/bin/env bash
set -e

echo "1. 在 util 包中查找所有 hooks 目录："
find node_modules/@rc-component/util -type d | grep -Ei 'hooks?$' || echo "→ 未找到 hooks 目录"

echo -e "\n2. 查找所有包含 useId 字样的文件："
find node_modules/@rc-component/util -type f | grep -i useid || echo "→ 未找到 useId 相关文件"

echo -e "\n3. 在这些文件中搜索 useId 的导出声明："
rg "export (default )?useId" node_modules/@rc-component/util || echo "→ 未检索到 useId 导出"

Length of output: 720

---

请确认 @rc-component/util 包已正确安装并且路径有效性
目前在 node_modules 中未找到 @rc-component/util，请按下列步骤核实：

• 运行 npm ls @rc-component/util（或 pnpm list @rc-component/util）检查依赖是否安装及版本是否为 ^1.2.1。
• 确认存在文件 node_modules/@rc-component/util/lib/hooks/useId，并且该文件通过 export default useId 导出了同 @rc-component/select 版本一致的接口。

如依赖未安装或路径不符，请先安装/升级依赖或修正导入路径后再合并。

✨ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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 99.83%. Comparing base (3aaa70c) to head (e1b23d3).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #599   +/-   ##
=======================================
  Coverage   99.83%   99.83%           
=======================================
  Files          23       23           
  Lines         611      611           
  Branches      186      176   -10     
=======================================
  Hits          610      610           
  Misses          1        1           

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