Fix deprecated findDOMNode usage in React 19 #909
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.
Update the library to remove the use of deprecated
findDOMNode
and replace it with a ref-based approach.NonStrictPanel.tsx
findDOMNode
withReact.createRef
to access the DOM element.nativeElement
getter to return the current ref.render
method to clone the element with the ref.ReactElementProvider.ts
StrictPanel
orNonStrictPanel
.element
getter to return the current ref.show
andhide
methods to use the ref.Flicking.tsx
useFindDOMNode
prop and use a ref-based approach._createPanelRefs
method to useReact.createRef
._getPanels
method to use the new ref-based approach.ReactRenderer.ts
_collectPanels
method to use the new ref-based approach._createPanel
method to use the new ref-based approach.package-lock.json
4.12.0-snapshot
.