feat: support popupItem

[thinkasany]

Summary by CodeRabbit

• 新功能
  • 增强了界面的样式定制能力，现在用户可以享受更灵活的弹窗项配置选项，提供更细致和个性化的视觉效果。
  • 优化了面板中展示元素的外观一致性，进一步提升了整体用户体验。

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
picker	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 20, 2025 8:07am

[coderabbitai]

Walkthrough

本次 PR 对 PickerPanel 组件及相关测试和类型声明进行了扩展更新。主要修改包括在 PanelBody.tsx 文件中为 <td> 元素添加新的 class 名 popupItem 及内联样式；在类型定义中（src/PickerPanel/index.tsx 和 src/interface.tsx）增加 popupItem 选项；以及在测试中增加对新属性的验证，提升了样式和语义配置的灵活性。

Changes

文件	变更摘要
src/PickerPanel/PanelBody.tsx	修改 <td> 元素的 className，添加 pickerClassNames?.popupItem，并新增 style 属性，使用 styles?.popupItem 应用内联样式。
src/PickerPanel/index.tsx src/interface.tsx	扩展类型定义，分别在 PanelSemanticName 与 SemanticStructure 中新增 popupItem 选项，支持新的语义样式配置。
tests/picker.spec.tsx	为测试用例增加 popupItem 属性的验证，在 customClassNames 与 customStyles 中新增相应配置，并添加了对 DOM 元素 class 和样式的断言。

Possibly related PRs

• feat: semantic support content、body #922: 类似地在组件中进行了样式和上下文管理的增强，与本次对 popupItem 的支持存在代码关联。
• feat: support semantic for panel #923: 对 PanelSemanticName 类型的扩展更新与本次修改直接相关，均涉及 popupItem 选项的引入。

Poem

我是跳跃的小兔，代码森林我自由驰骋，
新增 popupItem 点亮样式，如萝卜般清新亮丽，
类型扩展写下新诗篇，测试验证保驾护航，
在代码的世界里，快乐与创意共舞，
小兔献上微笑，愿每行代码都蕴藏魔法 🐇✨

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/PickerPanel/PanelBody.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

Error: Cannot read config file: /.eslintrc.js
Error: Cannot find module '@umijs/fabric/dist/eslint'
Require stack:

• /.eslintrc.js
• /node_modules/.pnpm/@eslint+eslintrc@2.1.4/node_modules/@eslint/eslintrc/dist/eslintrc.cjs
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli-engine/cli-engine.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/eslint.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/index.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/bin/eslint.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
  at Function.resolve (node:internal/modules/helpers:145:19)
  at Object. (/.eslintrc.js:2:21)
  at Module._compile (node:internal/modules/cjs/loader:1546:14)
  at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
  at Module.load (node:internal/modules/cjs/loader:1317:32)
  at Module._load (node:internal/modules/cjs/loader:1127:12)
  at TracingChannel.traceSync (node:diagnostics_channel:315:14)
  at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
  at Module.require (node:internal/modules/cjs/loader:1339:12)

src/PickerPanel/index.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

Error: Cannot read config file: /.eslintrc.js
Error: Cannot find module '@umijs/fabric/dist/eslint'
Require stack:

• /.eslintrc.js
• /node_modules/.pnpm/@eslint+eslintrc@2.1.4/node_modules/@eslint/eslintrc/dist/eslintrc.cjs
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli-engine/cli-engine.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/eslint.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/index.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/bin/eslint.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
  at Function.resolve (node:internal/modules/helpers:145:19)
  at Object. (/.eslintrc.js:2:21)
  at Module._compile (node:internal/modules/cjs/loader:1546:14)
  at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
  at Module.load (node:internal/modules/cjs/loader:1317:32)
  at Module._load (node:internal/modules/cjs/loader:1127:12)
  at TracingChannel.traceSync (node:diagnostics_channel:315:14)
  at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
  at Module.require (node:internal/modules/cjs/loader:1339:12)

src/interface.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

Error: Cannot read config file: /.eslintrc.js
Error: Cannot find module '@umijs/fabric/dist/eslint'
Require stack:

• /.eslintrc.js
• /node_modules/.pnpm/@eslint+eslintrc@2.1.4/node_modules/@eslint/eslintrc/dist/eslintrc.cjs
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli-engine/cli-engine.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/eslint.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/eslint/index.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/lib/cli.js
• /node_modules/.pnpm/eslint@8.57.1/node_modules/eslint/bin/eslint.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
  at Function.resolve (node:internal/modules/helpers:145:19)
  at Object. (/.eslintrc.js:2:21)
  at Module._compile (node:internal/modules/cjs/loader:1546:14)
  at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
  at Module.load (node:internal/modules/cjs/loader:1317:32)
  at Module._load (node:internal/modules/cjs/loader:1127:12)
  at TracingChannel.traceSync (node:diagnostics_channel:315:14)
  at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
  at Module.require (node:internal/modules/cjs/loader:1339:12)

• 1 others

---

📜 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 3eac54f and ea5d597.

📒 Files selected for processing (4)

• src/PickerPanel/PanelBody.tsx (2 hunks)
• src/PickerPanel/index.tsx (1 hunks)
• src/interface.tsx (1 hunks)
• tests/picker.spec.tsx (2 hunks)

🔇 Additional comments (8)

src/interface.tsx (1)

284-284: 支持 popupItem 语义结构

增加 popupItem 到 SemanticStructure 类型定义中扩展了弹出框内部元素的样式控制能力，与 src/PickerPanel/index.tsx 中的 PanelSemanticName 类型更新保持一致。

src/PickerPanel/PanelBody.tsx (2)

130-144: 为表格单元格添加 popupItem 类名支持

通过在 <td> 元素的 className 中加入 pickerClassNames?.popupItem，使表格单元格能够接收自定义类名，提高了组件的样式可定制性。

---

145-145: 为表格单元格添加 popupItem 样式支持

通过在 <td> 元素上添加 style={styles?.popupItem}，使表格单元格能够接收自定义内联样式，与类名支持相互配合，提供更完整的样式定制能力。

src/PickerPanel/index.tsx (1)

130-130: 扩展 PanelSemanticName 类型以支持 popupItem

将 popupItem 添加到 PanelSemanticName 类型中，使其与 src/interface.tsx 中的 SemanticStructure 类型保持一致，确保了组件样式定制的一致性和完整性。

tests/picker.spec.tsx (4)

1357-1359: 为测试添加 popupItem 自定义类名

在测试中添加 popupItem: 'custom-item' 以验证新增的 popupItem 语义名称是否能正确应用于组件。

---

1363-1365: 为测试添加 popupItem 自定义样式

在测试中添加 popupItem: { color: 'yellow' } 以验证新增的 popupItem 样式是否能正确应用于组件。

---

1372-1378: 添加 popupItem 类名和样式的测试验证

获取表格单元格元素并验证其是否正确应用了自定义的 popupItem 类名和样式，确保功能正常工作。

---

1384-1407: 为 PickerPanel 组件添加 popupItem 测试

为 PickerPanel 组件添加了相同的 popupItem 测试逻辑，确保在面板组件中同样可以应用自定义类名和样式，保持了一致性的测试覆盖。

✨ 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 98.79%. Comparing base (3eac54f) to head (ea5d597).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #924   +/-   ##
=======================================
  Coverage   98.79%   98.79%           
=======================================
  Files          64       64           
  Lines        2654     2654           
  Branches      739      739           
=======================================
  Hits         2622     2622           
  Misses         29       29           
  Partials        3        3           

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