mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Joshua GrossandFacebook GitHub Bot
b9828a8afa
Summary: I am fixing an extremely marginal case that probably impacts nothing in production, but in theory, could - see next diff in stack for the assert that is being hit. TL;DR in marginal, complex cases with a lot of un/flattening, we can generate the following sequence of mutations: ``` UPDATE node V1 -> V2 REMOVE node V1 ``` That is incorrect, and what we actually want is: ``` UPDATE node V1 -> V2 REMOVE node V2 ``` While this, again, impacts /nothing/ in prod that we know of, it would be good to get this correct so that we can enable stricter asserts (see next diff). This will also help with debugging LayoutAnimations. Changelog: [Internal] Reviewed By: mdvacca Differential Revision: D27697788 fbshipit-source-id: 47f34fe3e8107167b3df4db841d2cc14c58cb31d