-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[v4] Removed all usage of findDOMNode #1696
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
Conversation
48213e2
to
9576cf3
Compare
bulkActionButtonNode.getBoundingClientRect().width) || | ||
0; | ||
const width = (this.bulkActionButton | ||
.current as HTMLButtonElement).getBoundingClientRect().width; |
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.
This cast is to increase codecov. We don't optionally render the button so this ref will always exist in componentDidMount lifecycle
}); | ||
}); | ||
|
||
function FocusTestWrapper({children, ...props}: Discard<Props, 'root'>) { |
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.
Wrapper component that passes a root to Focus
cf9f4a2
to
9f979a6
Compare
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.
As per usual, looks great, works great 🎉 🚢
WHY are these changes introduced?
Last change before we can enable strict mode 🎉
WHAT is this pull request doing?
Luckily none of our uses require findDOMNode to find a child element without any context so we can replace them with refs.