-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Fix incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method #53863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…tryPoint.loadWithFeatureFlags() method Summary: In this diff I'm fixing an incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method. changelog: [internal] internal Differential Revision: D82841006
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review automatically exported from Phabricator review in Meta.
This pull request has been merged in 23b2b99. |
This pull request was successfully merged by @mdvacca in 23b2b99 When will my fix make it into a release? | How to file a pick request? |
…tryPoint.loadWithFeatureFlags() method (#53863) Summary: Pull Request resolved: #53863 In this diff I'm fixing an incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method. changelog: [internal] internal Reviewed By: cortinico Differential Revision: D82841006 fbshipit-source-id: 6f50f2475255d7b841d9224bc8808119dcc68aec
This pull request was successfully merged by @mdvacca in ea2d95a When will my fix make it into a release? | How to file a pick request? |
* Ensure legacy architecture can't be initialized in Android (#53806) Summary: Pull Request resolved: #53806 The Legacy architecture of React Native is not supported anymore, let's ensure nobody can initialize it anymore changelog: [internal] internal Reviewed By: cortinico Differential Revision: D82465004 fbshipit-source-id: 099764fb59d906b11cf6ad0cc6208f56df029d19 * Runtime check that NewArchitecture is enabled in DefaultNewArchitectureEntryPoint (#53780) Summary: Pull Request resolved: #53780 This is a commit we're going to pick in 0.82 as we want to make sure users cannot invoke `load()` from `DefaultNewArchitectureEntryPoint` with flags that are not true,true,true. Changelog: [Android] [Changed] - Runtime check that NewArchitecture is enabled in DefaultNewArchitectureEntryPoint Reviewed By: mdvacca Differential Revision: D82456975 fbshipit-source-id: 749996a3491913cfe400173608218077c3ffbc10 * Fix DefaultNewArchitectureEntryPoint config validation (#53807) Summary: Pull Request resolved: #53807 We need to read the values off feature flags before checking them. ## Changelog [Internal] Reviewed By: javache Differential Revision: D82572898 fbshipit-source-id: 09fbc09570c78b41d9c25fb03c5557e390da7cae * Fix incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method (#53863) Summary: Pull Request resolved: #53863 In this diff I'm fixing an incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method. changelog: [internal] internal Reviewed By: cortinico Differential Revision: D82841006 fbshipit-source-id: 6f50f2475255d7b841d9224bc8808119dcc68aec --------- Co-authored-by: David Vacca <[email protected]> Co-authored-by: Eric Rozell <[email protected]>
Summary:
In this diff I'm fixing an incorrect validation of feature flags in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags() method.
changelog: [internal] internal
Differential Revision: D82841006