Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: release plan template strategy types, constraints, segments #8861

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

daveleek
Copy link
Contributor

Adds different types of strategies and their properties to the strategy-add/edit dialog, along with constraints and segments

Skjermbilde 2024-11-26 kl  15 25 55
Skjermbilde 2024-11-26 kl  15 25 36

Copy link

vercel bot commented Nov 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 26, 2024 2:28pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
unleash-docs ⬜️ Ignored (Inspect) Nov 26, 2024 2:28pm

Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

@daveleek
Copy link
Contributor Author

There's some validation to add, but that will be a separate task

return <DefaultStrategy strategyDefinition={strategyDefinition} />;
case 'flexibleRollout':
return (
<MilestoneStrategyTypeFlexible
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one in feature strategies uses projectid and environment info, so had to take the relevant parts out and make a separate one specifically for this.

);
case 'userWithId':
return (
<UserWithIdStrategy
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This along with the other UIs (Default and General) are all imported from the feature strategies. Should we make our own here or is this good enough for now?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably good enough for now, let's come back to this later.

{!BuiltInStrategies.includes(strategy.name || 'default') && (
<StyledAlertBox>
<Alert severity='warning'>
Custom strategies are deprecated. We recommend not
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that custom strategies are deprecated, should we support them here at all?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO we can do the same as we do in feature strategies for now and return to this later. But it's good to bring it up.

@daveleek daveleek requested review from chriswk and nunogois November 26, 2024 14:31
Copy link
Member

@nunogois nunogois left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Following the philosophy of moving forward for now and coming back to clean this up later.

@daveleek daveleek merged commit 219006c into main Nov 27, 2024
12 of 13 checks passed
@daveleek daveleek deleted the feat/release-plan-templates-strategy-types branch November 27, 2024 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants