Unleash / unleash / 24122385116

87%

master: 91%

push

github

chore(AI): strategyFormConsolidation flag cleanup (#11739)

This PR cleans up the strategyFormConsolidation flag. These changes were
automatically generated by AI and should be reviewed carefully.

Fixes #11738

## 🧹 AI Flag Cleanup Summary
Cleaned up the `strategyFormConsolidation` feature flag by making the
consolidated strategy forms the default implementation and fully
deleting the
legacy components.
### 🚮 Removed
- **Feature Flag Definitions**
- Removed `strategyFormConsolidation` from `experimental.ts` and
`uiConfig.ts`.
- Removed `strategyFormConsolidation` from testing setups
(`server-dev.ts` and
`featureStrategyFormTestSetup.ts`).
- **Legacy Components**
- `OldFlexibleStrategy` in `FlexibleStrategy.tsx`.
- `LegacyFeatureStrategyType` in `FeatureStrategyType.tsx`.
- Removed legacy conditionals in `EditDefaultStrategy.tsx`,
`ReleasePlanTemplateAddStrategyForm.tsx`, `FeatureStrategyCreate.tsx`,
`ProjectDefaultStrategyForm.tsx`, `EditChange.tsx`, and
`FeatureStrategyEdit.tsx`.
- Deleted legacy files: `LegacyEditDefaultStrategy.tsx`,
`LegacyReleasePlanTemplateAddStrategyForm.tsx`,
`LegacyFeatureStrategyCreate.tsx`, `LegacyEditChange.tsx`, and
`LegacyFeatureStrategyEdit.tsx`.
### 🛠 Kept
- **Components**
- Retained the "new" consolidated components implicitly by making them
the
default exports (e.g. `FeatureStrategyCreate`, `FeatureStrategyEdit`,
`EditChange`, `ReleasePlanTemplateAddStrategyForm`,
`EditDefaultStrategy`).
### 📝 Why
The `strategyFormConsolidation` feature flag had an outcome of `kept`.
All logic
that reverted to the old, un-consolidated strategy forms could be safely
removed, ensuring that only the preferred, updated logic stays.

---------

Co-authored-by: unleash-bot <194219037+unleash-bot[bot]@users.noreply.github.com>
Co-authored-by: Thomas Heartman <thomas@getunleash.io>

1821 of 2012 branches covered (90.51%)

14975 of 17194 relevant lines covered (87.09%)

902.72 hits per line