Files
Krzysztof Magiera 438bb676b2 Fix evaluation logic to visit nodes that get marked as updated during eval loop.
After start/stop API landed we started evaluating graph of nodes in topological order. In order for that to work we needed to create a stack of final node to be evaluated and run it in particular order. What might happen during evaluation is that some new nodes can be marked as updated (e.g. we use set node to update a value in a different nodes subtree). In such a case we want to update views that newly marked node may have impact on.

Here we also changed Android to use ArrayList instead of SparseArray for the list of updated nodes. This is to make it consistent with iOS implementation where we use a regular list too. In practice it won't happen too often that a view is added to a queue several times. Even if that happens, we still will evaluate the node at most once per frame.
2018-08-08 11:23:31 +02:00
..
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00
2018-04-25 11:22:32 +02:00

README

If you want to publish the lib as a maven dependency, follow these steps before publishing a new version to npm:

  1. Be sure to have the Android SDK and NDK installed
  2. Be sure to have a local.properties file in this folder that points to the Android SDK and NDK
ndk.dir=/Users/{username}/Library/Android/sdk/ndk-bundle
sdk.dir=/Users/{username}/Library/Android/sdk
  1. Delete the maven folder
  2. Run sudo ./gradlew installArchives
  3. Verify that latest set of generated files is in the maven folder with the correct version number