refactor: update content to section

[thinkasany]

Summary by CodeRabbit

• 样式调整

  • 将抽屉组件的内容类名从 content 更改为 section
  • 更新了相关接口和测试用例中的类名引用

• 测试更新

  • 修改了测试用例中的类名选择器
  • 调整了样式和类名相关的断言

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
drawer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 7, 2025 9:50am

[coderabbitai]

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/DrawerPanel.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)

概述

演练

这个拉取请求主要涉及抽屉（Drawer）组件的类名和接口结构的重构。更改集中在将 content 相关的类名、样式和接口属性替换为 section。这些修改影响了 DrawerPanel、DrawerPopup、接口定义和相关测试文件，但未改变组件的核心功能。

变更

文件	变更摘要
src/DrawerPanel.tsx	将 div 元素的类名从 ${prefixCls}-content 更改为 ${prefixCls}-section
src/DrawerPopup.tsx	更新 panelNode 渲染逻辑中的类名和样式属性，从 content 改为 section
src/inter.ts	在 DrawerClassNames 和 DrawerStyles 接口中，移除 content 属性并添加 section 属性
tests/index.spec.tsx	更新测试选择器和断言，将 .rc-drawer-content 替换为 .rc-drawer-section
tests/ref.spec.tsx	修改 panelRef 元素类名的断言

诗歌

🐰 抽屉变装，轻轻一跃
内容换了个新名字
section 闪亮登场
代码如诗，优雅飞翔
重构的兔子笑开颜 🎉

---

📜 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 c3471c8 and e43b27c.

📒 Files selected for processing (5)

• src/DrawerPanel.tsx (1 hunks)
• src/DrawerPopup.tsx (1 hunks)
• src/inter.ts (1 hunks)
• tests/index.spec.tsx (7 hunks)
• tests/ref.spec.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/DrawerPanel.tsx

🔇 Additional comments (4)

src/inter.ts (1)

4-4: ⚠️ Potential issue

注意：这是一个破坏性更改

将 content 重命名为 section 是一个破坏性更改，会影响到使用这些接口的现有代码。建议：

1. 在发布说明中标记这是一个破坏性更改
2. 提供迁移指南

Also applies to: 10-10

tests/ref.spec.tsx (1)

23-23: 测试更新正确

测试断言已正确更新以匹配新的类名。

src/DrawerPopup.tsx (1)

301-301: 实现更改正确

类名和样式属性已正确更新，与接口变更保持一致。

Also applies to: 304-304

tests/index.spec.tsx (1)

304-306: 测试用例更新全面

所有测试用例都已正确更新以使用新的类名：

• 键盘事件测试
• 鼠标事件测试
• 类名断言
• 自定义类名测试
• 样式测试

测试覆盖率保持完整。

Also applies to: 315-317, 379-381, 389-392, 433-445, 455-468

---

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. (Beta)
• @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 100.00%. Comparing base (c3471c8) to head (e43b27c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #478   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          146       146           
  Branches        54        54           
=========================================
  Hits           146       146           

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