Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Bubble.List re-render #479

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

YumoImer
Copy link
Collaborator

@YumoImer YumoImer commented Jan 17, 2025

fix: #402

before

image

now

image

Summary by CodeRabbit

  • 性能优化

    • Bubble 组件中使用 React.useMemo 优化渲染性能
    • 通过缓存 avatarNodemergedContent 减少不必要的重新渲染
  • 数据处理

    • 移除 useDisplayData 钩子
    • 简化 BubbleList 组件的数据管理流程
    • 直接使用 mergedData 处理列表渲染和滚动逻辑
  • 新功能

    • 新增 Demo 组件用于调试和展示 Bubble 组件的功能
    • 在文档中增加调试列表示例代码
  • 文档更新

    • Bubble 组件的文档添加中英文调试列表示例说明

Copy link
Contributor

coderabbitai bot commented Jan 17, 2025

📝 Walkthrough

概述

遍历

Bubble.tsx 文件中,主要通过使用 React.useMemoavatarNodemergedContent 变量进行性能优化。新的实现通过记忆化(memoization)这些变量,确保只有在特定依赖项发生变化时才重新计算,从而减少不必要的重新渲染。变更专注于性能改进,未改变组件的核心功能。

BubbleList.tsx 文件中,移除了 useDisplayData 钩子,直接使用 mergedData 进行数据处理。此变更简化了状态管理,并更新了与滚动和渲染相关的逻辑。删除的 useDisplayData.ts 文件原本用于管理和显示项目列表的自定义钩子,其功能已被替代。

此外,debug-list.mddebug-list.tsx 文件中新增了调试相关的内容与示例,以帮助开发者验证 Bubble.List 的行为。

变更

文件 变更摘要
components/bubble/Bubble.tsx 使用 React.useMemo 优化 avatarNodemergedContent 的计算
components/bubble/BubbleList.tsx 移除 useDisplayData 钩子,直接使用 mergedData 进行数据处理,更新滚动和渲染逻辑
components/bubble/hooks/useDisplayData.ts 删除自定义钩子 useDisplayData
components/bubble/demo/debug-list.md 新增中文和英文调试说明
components/bubble/demo/debug-list.tsx 新增调试示例组件 Demo
components/bubble/index.en-US.md 新增调试列表示例代码
components/bubble/index.zh-CN.md 新增调试列表示例代码

评估与链接问题

目标 已解决 说明
历史消息如果内容没有变化,不应该更新 (#402)

可能相关的 PRs

建议审阅者

  • afc163

诗歌

🐰 兔子的性能优化诗 🚀
内存轻如风,渲染快如电
useMemo 护航,重绘不再烦
兔子代码跳,性能新篇展


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

Copy link

github-actions bot commented Jan 17, 2025

Preview is ready

Copy link

codecov bot commented Jan 17, 2025

Bundle Report

Bundle size has no change ✅

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
components/bubble/Bubble.tsx (1)

115-118: 建议:考虑 messageRender 的性能影响

使用 useMemo 缓存 mergedContent 是个好主意,但要注意以下几点:

  1. 如果 messageRender 是一个内联函数,每次渲染都会创建新的引用,这样会导致缓存失效
  2. 建议将 messageRender 也使用 useCallback 包装,以确保缓存的有效性

示例代码:

+ const memoizedMessageRender = React.useCallback(
+   (content: any) => messageRender(content),
+   [messageRender]
+ );

  const mergedContent = React.useMemo(
-   () => (messageRender ? messageRender(typedContent as any) : typedContent),
+   () => (messageRender ? memoizedMessageRender(typedContent as any) : typedContent),
    [typedContent, messageRender],
  );
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5380eb5 and 3f4e237.

📒 Files selected for processing (1)
  • components/bubble/Bubble.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: test / react component workflow
  • GitHub Check: build preview
  • GitHub Check: size
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: test / react component workflow
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (1)
components/bubble/Bubble.tsx (1)

109-112: 优化:使用 useMemo 缓存 avatarNode 是个好的改进!

通过 useMemo 缓存 avatarNode 可以避免在 avatar prop 没有变化时的不必要重渲染,这是一个很好的性能优化。依赖数组的设置也很准确。

Copy link

codecov bot commented Jan 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.66%. Comparing base (b88b550) to head (bde6134).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #479      +/-   ##
==========================================
+ Coverage   91.45%   91.66%   +0.21%     
==========================================
  Files          67       66       -1     
  Lines        1462     1440      -22     
  Branches      384      379       -5     
==========================================
- Hits         1337     1320      -17     
+ Misses        125      120       -5     

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

Copy link

github-actions bot commented Jan 17, 2025

size-limit report 📦

Path Size
dist/antdx.min.js 40.23 KB (-114 B 🔽)

Copy link

cloudflare-workers-and-pages bot commented Jan 17, 2025

Deploying ant-design-x with  Cloudflare Pages  Cloudflare Pages

Latest commit: 069de64
Status: ✅  Deploy successful!
Preview URL: https://8d09406c.ant-design-x.pages.dev
Branch Preview URL: https://refactor-bubble-list-rerende.ant-design-x.pages.dev

View logs

@YumoImer YumoImer requested a review from a team January 17, 2025 03:15
@afc163
Copy link
Member

afc163 commented Jan 17, 2025

需要加个测试用例么?

@YumoImer
Copy link
Collaborator Author

需要加个测试用例么?

感觉有必要,我想下怎么加好些。

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
components/bubble/BubbleList.tsx (3)

Line range hint 108-124: 建议增加空值检查以提高代码健壮性

当前代码在访问 mergedData[mergedData.length - 2] 时可能存在潜在的空值风险。建议添加额外的安全检查。

-const lastItemKey = mergedData[mergedData.length - 2]?.key;
+const secondLastItem = mergedData.length >= 2 ? mergedData[mergedData.length - 2] : null;
+const lastItemKey = secondLastItem?.key;

-const bubbleInst = bubbleRefs.current[lastItemKey!];
+if (!lastItemKey) {
+  return;
+}
+const bubbleInst = bubbleRefs.current[lastItemKey];

142-143: 建议添加注释说明滚动逻辑

这段代码负责更新滚动状态,建议添加注释以说明其目的和工作原理。

+// 更新滚动状态:如果滚动到最后一项,则标记为已到达底部
 const index = mergedData.findIndex((dataItem) => dataItem.key === key);
 setScrollReachEnd(index === mergedData.length - 1);

Line range hint 181-193: 优化气泡组件的引用管理逻辑

当前的引用管理逻辑可以通过使用回调函数来简化。同时,建议将 typing 属性的处理逻辑提取为一个单独的变量以提高可读性。

 {mergedData.map(({ key, ...bubble }) => {
+  const handleBubbleRef = (node: BubbleRef | null) => {
+    if (node) {
+      bubbleRefs.current[key] = node;
+    } else {
+      delete bubbleRefs.current[key];
+    }
+  };
+  const shouldShowTyping = initialized && bubble.typing;
+
   return (
     <Bubble
       {...bubble}
       key={key}
-      ref={(node) => {
-        if (node) {
-          bubbleRefs.current[key] = node;
-        } else {
-          delete bubbleRefs.current[key];
-        }
-      }}
-      typing={initialized ? bubble.typing : false}
+      ref={handleBubbleRef}
+      typing={shouldShowTyping}
     />
   );
 })}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4e237 and bde6134.

📒 Files selected for processing (2)
  • components/bubble/BubbleList.tsx (4 hunks)
  • components/bubble/hooks/useDisplayData.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • components/bubble/hooks/useDisplayData.ts
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: test / react component workflow
  • GitHub Check: build preview
  • GitHub Check: size
  • GitHub Check: test / react component workflow
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Cloudflare Pages

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (5)
components/bubble/BubbleList.tsx (3)

39-55: 优化组件引用(ref)的处理方式

当前实现中的引用处理较为复杂,建议进行以下改进:

  1. 使用 TypeScript 的类型断言替代强制类型转换
  2. 考虑使用 useImperativeHandle 来更优雅地处理引用
 const BubbleListItem: React.ForwardRefRenderFunction<Record<string, BubbleRef>, BubbleProps> = (
   props,
   ref,
 ) => (
   <Bubble
     {...props}
-    ref={(node) => {
-      if (node) {
-        (ref as React.RefObject<Record<string, BubbleRef>>).current[props.id!] = node;
-      } else {
-        delete (ref as React.RefObject<Record<string, BubbleRef>>).current?.[props.id!];
-      }
-    }}
+    ref={(node) => {
+      const refMap = (ref as React.MutableRefObject<Record<string, BubbleRef>>).current;
+      if (node) {
+        refMap[props.id!] = node;
+      } else {
+        delete refMap?.[props.id!];
+      }
+    }}
   />
 );

Line range hint 126-142: 增强滚动逻辑的健壮性

当前的滚动逻辑可能在边缘情况下出现问题:

  1. 需要添加数组长度检查
  2. 建议为关键的魔术数字添加注释说明
-      const lastItemKey = mergedData[mergedData.length - 2]?.key;
+      // 获取倒数第二个项目作为滚动触发点,以确保新消息出现时能平滑滚动
+      const lastItemKey = mergedData.length >= 2 
+        ? mergedData[mergedData.length - 2]?.key 
+        : mergedData[mergedData.length - 1]?.key;
       const bubbleInst = bubbleRefs.current[lastItemKey!];

-      if (bubbleInst) {
+      if (bubbleInst && listRef.current) {

160-161: 优化键值查找性能

当前使用 findIndex 进行线性查找可能在大型列表中造成性能问题。建议考虑使用 Map 来优化查找性能。

+          // 使用 Map 存储 key 到 index 的映射
+          const keyIndexMap = new Map(mergedData.map((item, index) => [item.key, index]));
+          const index = keyIndexMap.get(key) ?? -1;
-          const index = mergedData.findIndex((dataItem) => dataItem.key === key);
           setScrollReachEnd(index === mergedData.length - 1);
components/bubble/demo/debug-list.tsx (2)

21-38: 建议改进 ID 生成逻辑

当前的 ID 生成方式可能会在边界情况下产生问题。建议使用更可靠的唯一标识符生成方式。

-    const id = `${firstId !== undefined ? Number(firstId) - 1 : 0}`;
+    const id = `${Date.now()}-${Math.random().toString(36).slice(2)}`;

58-70: 建议增加错误处理机制

建议在以下场景添加错误处理:

  1. deleteBubble 找不到指定 ID 时的处理
  2. scrollTo 滚动失败时的错误提示
 function deleteBubble(id: string) {
+  const originalLength = bubbleList.length;
   setBubbleList((preList) => preList.filter((item) => item.id !== id));
+  if (bubbleList.length === originalLength) {
+    message.warning(`未找到 ID 为 ${id} 的消息`);
+    return;
+  }
   message.success(`#${id} message deleted!`);
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bde6134 and 069de64.

📒 Files selected for processing (5)
  • components/bubble/BubbleList.tsx (5 hunks)
  • components/bubble/demo/debug-list.md (1 hunks)
  • components/bubble/demo/debug-list.tsx (1 hunks)
  • components/bubble/index.en-US.md (1 hunks)
  • components/bubble/index.zh-CN.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • components/bubble/demo/debug-list.md
🧰 Additional context used
🪛 GitHub Actions: ✅ test
components/bubble/demo/debug-list.tsx

[error] 75-75: Snapshot test failed - new snapshot needs to be written but CI environment prevents automatic updates

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (7)
components/bubble/BubbleList.tsx (1)

199-205: 渲染逻辑优化得当

使用 MemoBubbleListItemmergedData 的直接渲染方式很好地优化了性能。建议为 typing 状态添加更明确的类型定义。

+            // 仅在组件初始化后启用打字动画
             typing={initialized ? bubble.typing : false}
components/bubble/demo/debug-list.tsx (4)

1-6: 代码结构清晰,类型定义恰当!

导入声明和类型定义组织得当,增强了代码的可维护性。


10-17: 建议优化初始状态的 typing 属性设置

初始状态中的 typing: true 可能会导致不必要的打字动画效果。如果这不是特意为之,建议移除该属性或设置为 false


71-101: 布局结构合理,性能优化到位!

  • 使用 useMemo 优化了选项列表的性能
  • 采用 Flex 组件实现了清晰的布局结构
🧰 Tools
🪛 GitHub Actions: ✅ test

[error] 75-75: Snapshot test failed - new snapshot needs to be written but CI environment prevents automatic updates


1-107: 需要更新快照测试

CI 环境显示快照测试失败。请在本地运行以下命令更新快照:

🧰 Tools
🪛 GitHub Actions: ✅ test

[error] 75-75: Snapshot test failed - new snapshot needs to be written but CI environment prevents automatic updates

components/bubble/index.zh-CN.md (1)

23-23: 文档更新正确!

新增的调试列表示例位置恰当,有助于开发者理解组件功能。

components/bubble/index.en-US.md (1)

22-22: 文档同步更新完善!

英文文档与中文文档保持同步,新增的调试列表示例有助于国际开发者理解组件功能。

components/bubble/demo/debug-list.tsx Show resolved Hide resolved
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.

使用Bubble.list 渲染消息时,历史消息内部也在 reRender
2 participants