fix: force update to keep disable state work

[aojunhao123]

ref ant-design/ant-design#51759 (comment)

强制re-render一下，处理缓存重置后状态不同步的问题，这么做会导致多一次渲染，对性能可能有点影响。或许还有更好的解法（

效果：

Summary by CodeRabbit

Summary by CodeRabbit

• 新功能
  • 改进了 OptionList 组件对禁用状态的管理，使其更加响应式。
• 修复
  • 优化了禁用状态缓存的清理逻辑，确保状态更新时能够正确触发重新渲染。

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
tree-select	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 25, 2024 3:31am

[coderabbitai]

概述

演练

此拉取请求修改了 src/OptionList.tsx 中的 OptionList 组件，主要增强了对树节点禁用状态的管理。引入了新的状态变量 disabledCache，替代了之前的 disabledCacheRef，使得禁用状态的缓存管理更加响应式。更新了在 leftMaxCount 变化时清除缓存的逻辑，确保禁用状态的更新能够正确触发重新渲染。组件的整体结构保持不变，但禁用状态的处理与 React 的状态管理更加紧密集成。

变更

文件	变更摘要
src/OptionList.tsx	- 添加 const [disabledCache, setDisabledCache] = React.useState<Map<string, boolean>>(new Map()) 状态变量 - 更新 getDisabledWithCache 方法以适应新的状态管理逻辑

可能相关的 PR

• feat: supplement maxCount logic for complicated cases #602：增强 TreeSelect 组件中 maxCount 功能的实现，与本 PR 在节点选择和禁用状态管理方面有直接关联

诗歌

🐰 选项清单，状态重生
缓存清空，节点轻盈
leftMaxCount 舞动轻风
重渲染，逻辑通明
兔子微笑，代码飞扬 🌈

---

📜 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 a5b1e9b and 4f4b124.

📒 Files selected for processing (1)

• src/OptionList.tsx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/OptionList.tsx

---

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 (2943745) to head (4f4b124).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #612   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           16        16           
  Lines          598       598           
  Branches       186       184    -2     
=========================================
  Hits           598       598           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/OptionList.tsx (1)

165-168: 强制触发组件更新可能导致额外的渲染开销

此处通过setForceUpdate({})强制组件重新渲染，虽然可以确保清空缓存后被动计算的逻辑正确触发，但也带来多一次不必要的渲染。建议评估此做法对性能的影响，如果有更精细的依赖管理或数据结构可以减少渲染次数，会更优。

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2943745 and c098a17.

📒 Files selected for processing (1)

• src/OptionList.tsx (1 hunks)

🔇 Additional comments (1)

src/OptionList.tsx (1)

169-176: 清空缓存与强制更新的调用顺序可读性较好，建议强调兼容情况

在leftMaxCount变化后清空缓存并触发重新渲染对逻辑正确性有帮助，但需注意以下几点：

1. 当leftMaxCount为0或小于0时，是否同样需要清空缓存并阻止用户选取？
2. 如果存在和此逻辑相关的其他依赖项，建议在注释中进一步说明，以便后续维护者快速理解强制更新的原因和流程。