Introduction
A lot of newer React Native improvements are currently gated behind flags and it's for good reason: it's unstable and not yet tested thoroughly with the partners, etc. However the community may want to experiment with the specific flags to test whether their application might work with new features, or adopting and testing out the new improvements and contribute to the upstream before the issues affects more broad userbase.
Details
Similar to Release Levels allow users to opt-in to select flags via APIs.
This was once possible via the ReactNativeFeatureFlags.override API but is effectively disabled with the introduction of New Arch, as DefaultNewArchitectureEntryPoint (Android) or RCTReactNativeFactory (iOS) will override the flags based on the release level.
Discussion points
- Some flags are meant to be enabled together, but the current feature flag system lacks a way to express that.
Introduction
A lot of newer React Native improvements are currently gated behind flags and it's for good reason: it's unstable and not yet tested thoroughly with the partners, etc. However the community may want to experiment with the specific flags to test whether their application might work with new features, or adopting and testing out the new improvements and contribute to the upstream before the issues affects more broad userbase.
Details
Similar to Release Levels allow users to opt-in to select flags via APIs.
This was once possible via the ReactNativeFeatureFlags.override API but is effectively disabled with the introduction of New Arch, as
DefaultNewArchitectureEntryPoint(Android) orRCTReactNativeFactory(iOS) will override the flags based on the release level.Discussion points