fix: Progress throws warning findDOMNode is deprecated in StrictMode
#42241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[中文版模板 / Chinese template]
🤔 This is a ...
🔗 Related issue link
💡 Background and solution
📝 Changelog
findDOMNode is deprecated in StrictMode
☑️ Self-Check before Merge
🚀 Summary
🤖 Generated by Copilot at 33029d7
Added ref forwarding and a new test case for the
Progress
component. This improves the component's compatibility with React strict mode and other components that use refs, such asTooltip
.🔍 Walkthrough
🤖 Generated by Copilot at 33029d7
Progress
component inReact.forwardRef
and passref
prop todiv
element to support ref forwarding (link,link,link,link)Tooltip
component fromantd
and add test case forProgress
component wrapped inTooltip
component to check for no strict mode warning (link,link)ProgressTypes
type fromprogress.tsx
toindex.test.tsx
to avoid circular dependency issue (link,link)