You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ea3b825
Browse filesBrowse the repository at this point in the historyBrowse files
Move unstable_batchedUpdates out of the renderer implementation API (#56567)
Summary:
Pull Request resolved: #56567
Changelog: [internal]
`unstable_batchedUpdates` was only ever defined in Paper, where it batched state updates triggered by an event handler. Some product code in apps using only Fabric imported it directly from Paper, where it was a no-op. After Paper was removed from React Native, the no-op was kept in `RendererImplementation` (and forwarded through `RendererProxy`) purely to preserve that compatibility — it has nothing to do with the Fabric renderer indirection that the rest of `RendererImplementation` is for.
Drop it from the renderer implementation API and define the no-op directly at the `react-native` package boundary:
- `index.js.flow` and `index.js` now define `unstable_batchedUpdates` inline (the public re-export already came from the package, so consumers using `import {unstable_batchedUpdates} from 'react-native'` are unaffected).
- Remove the corresponding `unstable_batchedUpdates` definitions / re-exports from `RendererImplementation.js`, `RendererProxy.fb.js`, and the `jest-preset` mock.
Reviewed By: javache
Differential Revision: D101989236
fbshipit-source-id: 9d83668f0dbc108ec24371fba37ed7ce7b452978
0 commit comments