Skip to content
FlagLint

OpenFeature Boundary

The migration goal is not to remove LaunchDarkly on day one. The goal is to move application-facing evaluation calls to OpenFeature.

Provider Architecture Diagram

Section titled “Provider Architecture Diagram”
Application code
  -> OpenFeature client
  -> LaunchDarkly OpenFeature provider
  -> LaunchDarkly

Before

Section titled “Before”
return ldClient.boolVariation("checkout-v2", ctx, false);

After

Section titled “After”
return openFeatureClient.getBooleanValue("checkout-v2", false, ctx);

FlagLint preserves the original flag key, fallback, and context expression. Provider/bootstrap setup is separate and must be reviewed by the platform team.

Why This Helps

Section titled “Why This Helps”

Once application code evaluates through OpenFeature, teams can enforce a single boundary in CI and keep provider-specific setup centralized.

Feedback

Section titled “Feedback”