mirror of
https://github.com/Unleash/unleash.git
synced 2025-10-27 11:02:16 +01:00
b8cdd1d004
https://linear.app/unleash/issue/2-3865/add-newstrategymodal-feature-flag Adds `newStrategyModal` feature flag. The approach here is to duplicate the existing `FeatureStrategyMenuCards` into a `LegacyFeatureStrategyMenuCards`. We'll continue working on the `FeatureStrategyMenuCards` component while leaving `LegacyFeatureStrategyMenuCards` untouched. Once we're done with the implementation and remove the flag we can drop the legacy file. I think it's easier to reduce our add strategy buttons to a single one right away (like we did with the `addConfiguration` flag in https://github.com/Unleash/unleash/pull/10420). This allows us to focus on the end result instead of having to implement things like "clicking the 'add release template' button should show the modal filtered to only release templates". <img width="735" height="126" alt="image" src="https://github.com/user-attachments/assets/6d10fab2-d091-40f3-9c36-05a6f28f7dda" /> <img width="995" height="742" alt="image" src="https://github.com/user-attachments/assets/a0fb9366-89b5-44e1-a684-47ee30d6d36c" /> |
||
|---|---|---|
| .. | ||
| action.ts | ||
| application.ts | ||
| banner.ts | ||
| connectedEdge.ts | ||
| context.ts | ||
| environments.ts | ||
| featureToggle.ts | ||
| featureTypes.ts | ||
| group.ts | ||
| instance.ts | ||
| integrationEvent.ts | ||
| invoice.ts | ||
| loginEvent.ts | ||
| permissions.ts | ||
| personalAPIToken.ts | ||
| project.ts | ||
| publicSignupTokens.ts | ||
| releasePlans.ts | ||
| role.ts | ||
| route.ts | ||
| segment.ts | ||
| service-account.ts | ||
| signal.ts | ||
| strategy.ts | ||
| tags.ts | ||
| toast.ts | ||
| token.ts | ||
| trafficBundles.ts | ||
| uiConfig.ts | ||
| user.ts | ||
| userProjectRoles.ts | ||