-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
base: main
Are you sure you want to change the base?
Conversation
📝 Walkthrough概述遍历在 在 此外, 变更
评估与链接问题
可能相关的 PRs
建议审阅者
诗歌
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Bundle ReportBundle size has no change ✅ |
There was a problem hiding this 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 是个好主意,但要注意以下几点:
- 如果 messageRender 是一个内联函数,每次渲染都会创建新的引用,这样会导致缓存失效
- 建议将 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
📒 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 没有变化时的不必要重渲染,这是一个很好的性能优化。依赖数组的设置也很准确。
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. |
size-limit report 📦
|
Deploying ant-design-x with Cloudflare Pages
|
需要加个测试用例么? |
感觉有必要,我想下怎么加好些。 |
There was a problem hiding this 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
📒 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
There was a problem hiding this 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)的处理方式当前实现中的引用处理较为复杂,建议进行以下改进:
- 使用 TypeScript 的类型断言替代强制类型转换
- 考虑使用
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
: 增强滚动逻辑的健壮性当前的滚动逻辑可能在边缘情况下出现问题:
- 需要添加数组长度检查
- 建议为关键的魔术数字添加注释说明
- 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
: 建议增加错误处理机制建议在以下场景添加错误处理:
deleteBubble
找不到指定 ID 时的处理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
📒 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
: 渲染逻辑优化得当使用
MemoBubbleListItem
和mergedData
的直接渲染方式很好地优化了性能。建议为 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
: 文档同步更新完善!英文文档与中文文档保持同步,新增的调试列表示例有助于国际开发者理解组件功能。
fix: #402
before
now
Summary by CodeRabbit
性能优化
Bubble
组件中使用React.useMemo
优化渲染性能avatarNode
和mergedContent
减少不必要的重新渲染数据处理
useDisplayData
钩子BubbleList
组件的数据管理流程mergedData
处理列表渲染和滚动逻辑新功能
Demo
组件用于调试和展示Bubble
组件的功能文档更新
Bubble
组件的文档添加中英文调试列表示例说明