Run flaglint migrate ./src --dry-run and you will see two kinds of results: call
sites with a generated diff and call sites marked skip — manual review required.
The skipped calls are not bugs in the tool. They are patterns where a mechanical
rewrite would change runtime behavior in ways the tool cannot prove are safe.
This article covers the five patterns that produce skips and what you need to do for each.
A provider outage can expose how deeply application code depends on a single feature-flag SDK. OpenFeature creates a neutral application boundary without forcing teams to abandon LaunchDarkly.
This article walks through the local audit, migration preview, and CI enforcement path that lets teams add that boundary incrementally.
LaunchDarkly and OpenFeature both evaluate flags with three arguments, but the fallback and context positions are reversed. A naive codemod can produce valid-looking code that silently changes runtime behavior.
This article shows the argument-order trap and why FlagLint uses AST analysis before rewriting any call site.