mirror of
https://github.com/zhigang1992/react-native-reanimated.git
synced 2026-01-12 22:50:47 +08:00
## Motivation I attach example illustrating this issue. The problem appears when we use `evaluateOnce` method (e.g. via `setValue`) for updating node which could be detached in the same time. ## Changes I observe I haven't deeply understood flow of reanimataed while writing this logic. Actually always node representing evaluation should not have children which has be informed about changes (it's pointless). In fact, always node has to be a child of these nodes, because we want to have these nodes attached (make them not sensitive for other detachments), because they states input for given node.
Run the example
- Clone the repository
- Run
yarnto install the dependencies of library cdto this directory- Run
yarnto install the dependencies of example - Run
yarn startto start the packager with custom config react-native run-iosorreact-native run-android