特征标志
- 作者仓库星标 245,422
- 作者仓库 react
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @facebook · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# React Feature Flags
## Flag Files
| File | Purpose |
|------|---------|
| `packages/shared/ReactFeatureFlags.js` | Default flags (canary), `__EXPERIMENTAL__` overrides |
| `packages/shared/forks/ReactFeatureFlags.www.js` | www channel, `__VARIANT__` overrides |
| `packages/shared/forks/ReactFeatureFlags.native-fb.js` | React Native, `__VARIANT__` overrides |
| `packages/shared/forks/ReactFeatureFlags.test-renderer.js` | Test renderer |
## Gating Tests
### `@gate` pragma (test-level)
Use when the feature is completely unavailable without the flag:
```javascript
// @gate enableViewTransition
it('supports view transitions', () => {
// This test only runs when enableViewTransition is true
// and is SKIPPED (not failed) when false
});
```
### `gate()` inline (assertion-level)
Use when the feature exists but behavior differs based on flag:
```javascript
it('renders component', async () => {
await act(() => root.render(<App />));
if (gate(flags => flags.enableNewBehavior)) {
expect(container.textContent).toBe('new output');
} else {
expect(container.textContent).toBe('legacy output');
}
});
```
## Adding a New Flag
1. Add to `ReactFeatureFlags.js` with default value
2. Add to each fork file (`*.www.js`, `*.native-fb.js`, etc.)
3. If it should vary in www/RN, set to `__VARIANT__` in the fork file
4. Gate tests with `@gate flagName` or inline `gate()`
## Checking Flag States
Use `/flags` to view states across channels. See the `flags` skill for full command options.
## `__VARIANT__` Flags (GKs)
Flags set to `__VARIANT__` simulate gatekeepers - tested twice (true and false):
```bash
/test www <pattern> # __VARIANT__ = true
/test www variant false <pattern> # __VARIANT__ = false
```
## Debugging Channel-Specific Failures
1. Run `/flags --diff <channel1> <channel2>` to compare values
2. Check `@gate` conditions - test may be gated to specific channels
3. Run `/test <channel> <pattern>` to isolate the failure
4. Verify flag exists in all fork files if newly added
## Common Mistakes
- **Forgetting both variants** - Always test `www` AND `www variant false` for `__VARIANT__` flags
- **Using @gate for behavior differences** - Use inline `gate()` if both paths should run
- **Missing fork files** - New flags must be added to ALL fork files, not just the main one
- **Wrong gate syntax** - It's `gate(flags => flags.name)`, not `gate('name')`
章节与文件索引
按说明文件中的顺序排列。
标记文件
@gate pragma(测试级别)
gateway() 内联(断言级别)
添加新标志
检查船旗国
文件/命令 -> packages/shared/ReactFeatureFlags.js · __EXPERIMENTAL__ · packages/shared/forks/ReactFeatureFlags.www.js · __VARIANT__ · packages/shared/forks/ReactFeatureFlags.native-fb.js · packages/shared/forks/ReactFeatureFlags.test-renderer.js · @gate · gate()
内容校验值 -> ab070c03162b
当前原文的自动摘译,尚未人工审校。
标记文件
文件·用途
packages/shared/ReactFeatureFlags.js·默认标志(金丝雀),__EXPERIMENTAL__覆盖packages/shared/forks/ReactFeatureFlags.www.js·www频道,__VARIANT__覆盖packages/shared/forks/ReactFeatureFlags.native-fb.js·React Native,__VARIANT__覆盖packages/shared/forks/ReactFeatureFlags.test-renderer.js·测试渲染器@gate pragma(测试级别)
当该功能在没有标志的情况下完全不可用时使用:
gateway() 内联(断言级别)
当该功能存在但行为因标志而异时使用:
添加新标志
使用默认值添加到
ReactFeatureFlags.js添加到每个 fork 文件(*.www.js、*.native-fb.js等) 如果 www/RN 中的内容有所不同,请在 fork 文件中设置为__VARIANT__使用@gate flagName或内联gate()进行门测试检查船旗国
使用
/flags查看跨通道的状态。有关完整命令选项,请参阅flags技能。