Skip to content

Conversation

@zombieJ
Copy link
Member

@zombieJ zombieJ commented Apr 8, 2025

改动

  • preview.classNames -> classNames.popup
  • preview.styles -> styles.popup

为何这么改

@thinkasany 聊下来 classNames 为唯一入口,子级组件都从 classNames 中走。以统一复杂结构的逻辑。例如 Transfer 组件使用了 Dropdown、Pagination、Input.Search 组件,但是本身并没有透出对应的 API 进行配置子组件的能力。如果是散装配置则需要每个都提供一个仅能配置 classNamesstyles 的一级入口,会非常怪异。统一收口后,使用复合子组件的场景不需要额外打孔即可支持。

Summary by CodeRabbit

  • 新功能

    • 增强了图像预览的样式配置功能,现在可以对弹出效果单独定制类名和样式,为用户带来更灵活的视觉自定义体验。
  • 重构

    • 统一并简化了预览组件中样式和类名的命名体系,优化了配置结构,使整体设置更直观高效。

@vercel
Copy link

vercel bot commented Apr 8, 2025

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

Name Status Preview Comments Updated (UTC)
image ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 8, 2025 11:34am

@coderabbitai
Copy link

coderabbitai bot commented Apr 8, 2025

Walkthrough

本次更改统一了预览组件相关的类型定义和接口结构。主要调整了 Image、Preview、PreviewGroup 组件以及相关钩子和测试用例中 classNames 与 styles 的声明方式,增加了 popup 子属性。与此同时,重命名了部分类型(如 InternalPreviewSemanticName → PreviewSemanticName)以及接口(GroupConsumerProps → PreviewGroupProps),并更新了参数传递与内部渲染逻辑,确保新结构的一致性。

Changes

文件 变更摘要
src/Image.tsx 更新类型导入;移除 PreviewConfig 中的 classNames 和 styles,调整 ImageProps 接口,新增 popup 属性;更新内部逻辑引用。
src/Preview/index.tsx 将 InternalPreviewSemanticName 重命名为 PreviewSemanticName;更新接口中对 classNames 与 styles 的类型引用。
src/PreviewGroup.tsx 重命名 GroupConsumerProps 为 PreviewGroupProps;为接口添加 classNames 与 styles 的 popup 配置;更新组件内参数传递。
src/hooks/usePreviewItems.ts 更新 items 参数类型,从 GroupConsumerProps['items'] 改为 PreviewGroupProps['items']。
tests/preview.test.tsx 调整测试用例,更新对 classNames 与 styles 的断言以匹配嵌套的 popup 结构。

Sequence Diagram(s)

sequenceDiagram
    participant PG as PreviewGroup
    participant P as Preview
    participant I as Image
    PG->>P: 传递 classNames.popup 与 styles.popup
    P->>I: 转发 popup 属性给 Image
    I->>I: 内部逻辑使用新的 classNames 与 styles 渲染
Loading

Possibly related PRs

Suggested reviewers

  • thinkasany

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/Image.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.

tests/preview.test.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.

src/PreviewGroup.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 385e131 and 4e31fd6.

📒 Files selected for processing (3)
  • src/Image.tsx (5 hunks)
  • src/PreviewGroup.tsx (3 hunks)
  • tests/preview.test.tsx (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • src/PreviewGroup.tsx
  • tests/preview.test.tsx
  • src/Image.tsx

🪧 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
Copy link

codecov bot commented Apr 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.40%. Comparing base (9d4b76c) to head (4e31fd6).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #404      +/-   ##
==========================================
- Coverage   99.40%   99.40%   -0.01%     
==========================================
  Files          17       17              
  Lines         506      504       -2     
  Branches      148      146       -2     
==========================================
- Hits          503      501       -2     
  Misses          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.

@zombieJ zombieJ changed the title test: fix test logic refactor: Move semantic props Apr 8, 2025
@zombieJ zombieJ merged commit e71f1fd into master Apr 8, 2025
10 checks passed
@zombieJ zombieJ deleted the refactor-semantic branch April 8, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants