3 ms·
Two major issues with the old context API: - It was a single shared key/value namespace, which could potentially lead to different libraries attempting to put
by acemarke 9y ago
Two major issues with the old context API:
- It was a single shared key/value namespace, which could potentially lead to different libraries attempting to put values at the same key and stomping on each other
- It was fine for passing down _initial_ values, but if you tried to _update_ a value, any components that returned `false` from `shouldComponentUpdate` would block their descendants from receiving the updated context values