Adding a New Feature Flag

A WCP license is required for feature flags to work. The license is the gate; the config is the switch within the gate.

Decision Flow

1. No license at all             → false (everything off, config ignored)
2. License blocks the flag       → false (config ignored)
3. License allows + config=false → false (config can disable what license allows)
4. License allows + config=true  → true
5. License allows + config unset → true  (license is the authority for unset flags)
6. Not in LICENSE_CHECKS + license exists + config unset → true
7. Not in LICENSE_CHECKS + license exists + config=false → false

Key points:

• Config can disable what the license allows, but cannot enable what the license blocks.
• Flags not governed by a license (LICENSE_CHECKS) still require a license to exist, then config decides.
• Without any license, all flags are off regardless of config.

Architecture

• FeatureFlags class (packages/feature-flags/src/FeatureFlags.ts), single isEnabled(name) method resolves dot-path strings against the DTO. Flags are disabled by default (undefined → false). Also provides isExplicitlyDisabled(name) to distinguish "not set" from "set to false".
• IFeatureFlagsDto (packages/feature-flags/src/types.ts), the typed DTO interface.
• KnownFeatureFlag (packages/feature-flags/src/FeatureFlags.ts), string literal union for autocomplete.
• Zod schema (packages/project/src/extensions/FeatureFlags.tsx), validates the config input.
• toDto() returns the fully resolved state (all flags explicitly set), used by the featureFlags GraphQL query.
• License decorators intercept isEnabled() and apply the decision flow above via a LICENSE_CHECKS map.

Steps to Add a Simple Boolean Flag

1. Add to DTO type

File: packages/feature-flags/src/types.ts

Add the new flag to IFeatureFlagsDto: