Noop: ReactInstance: Add todo above getRuntimeScheduler()#43952
Noop: ReactInstance: Add todo above getRuntimeScheduler()#43952RSNara wants to merge 1 commit intofacebook:mainfrom
Conversation
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
Base commit: f77d028 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
Summary: getRuntimeScheduler() allows things to schedule work on the js thread by bypassing main bundle buffering. This is unsafe: almost everything should be using the buffered runtime executor, unless it sets up bindings used in the main bundle. I filed a task for the investigation to see if there's any problems. And added it to the code in this diff. Changelog: [Internal] Reviewed By: cipolleschi Differential Revision: D55547899
|
This pull request was exported from Phabricator. Differential Revision: D55547899 |
…acebook#43952) Summary: getRuntimeScheduler() allows things to schedule work on the js thread by bypassing main bundle buffering. This is unsafe: almost everything should be using the buffered runtime executor, unless it sets up bindings used in the main bundle. I filed a task for the investigation to see if there's any problems. And added it to the code in this diff. Changelog: [Internal] Reviewed By: cipolleschi Differential Revision: D55547899
…acebook#43952) Summary: getRuntimeScheduler() allows things to schedule work on the js thread by bypassing main bundle buffering. This is unsafe: almost everything should be using the buffered runtime executor, unless it sets up bindings used in the main bundle. I filed a task for the investigation to see if there's any problems. And added it to the code in this diff. Changelog: [Internal] Reviewed By: cipolleschi Differential Revision: D55547899
|
This pull request has been merged in 9ad7138. |
|
This pull request was successfully merged by @RSNara in 9ad7138. When will my fix make it into a release? | How to file a pick request? |
Summary:
getRuntimeScheduler() allows things to schedule work on the js thread by bypassing main bundle buffering.
This is unsafe: almost everything should be using the buffered runtime executor, unless it sets up bindings used in the main bundle.
I filed a task for the investigation to see if there's any problems. And added it to the code in this diff.
Changelog: [Internal]
Reviewed By: cipolleschi
Differential Revision: D55547899