Skip to content
This repository was archived by the owner on Feb 8, 2020. It is now read-only.

fix: don't call getNode if ref is already scrollable#162

Merged
satya164 merged 1 commit intoreact-navigation:masterfrom
janicduplessis:fix-get-node-warn
Nov 8, 2019
Merged

fix: don't call getNode if ref is already scrollable#162
satya164 merged 1 commit intoreact-navigation:masterfrom
janicduplessis:fix-get-node-warn

Conversation

@janicduplessis
Copy link
Copy Markdown
Contributor

facebook/react-native@66e72bb deprecates getNode since Animated components now use React.forwardRef. To avoid triggering the warning I added a check to see if the node is already a scrollable node before trying to call the various method to get the scrollable node. This avoids calling getNode in newer RN versions.

@codecov-io
Copy link
Copy Markdown

Codecov Report

Merging #162 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #162   +/-   ##
=======================================
  Coverage   93.27%   93.27%           
=======================================
  Files          36       36           
  Lines         758      758           
  Branches      192      200    +8     
=======================================
  Hits          707      707           
  Misses         42       42           
  Partials        9        9

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 270fbdc...e4a670a. Read the comment docs.

@satya164 satya164 merged commit 66551f2 into react-navigation:master Nov 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants